Triple
T4749483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral of the Blue |
E105442
|
entity |
| Predicate | rankOrderInSystem |
P34755
|
FINISHED |
| Object | junior admiral of the three colour squadrons |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: junior admiral of the three colour squadrons | Statement: [Admiral of the Blue, rankOrderInSystem, junior admiral of the three colour squadrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOrderInSystem Context triple: [Admiral of the Blue, rankOrderInSystem, junior admiral of the three colour squadrons]
-
A.
rankStatus
chosen
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
B.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
C.
rankWithinOrganization
Indicates the relative hierarchical position or level an entity holds within a specific organization.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankInProtocol
Indicates the relative position or precedence an entity holds within an ordered protocol or formal hierarchy.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c6f5ac81908a62f9c17e77ac86 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.