Triple
T29750112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French military hierarchy |
E752869
|
entity |
| Predicate | definesRankStructureFor |
P2727
|
FINISHED |
| Object | officers |
—
|
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: officers | Statement: [French military hierarchy, definesRankStructureFor, officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesRankStructureFor Context triple: [French military hierarchy, definesRankStructureFor, officers]
-
A.
usesRankStructure
chosen
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
B.
rankStructureIncludes
Indicates that a given rank structure contains or encompasses a specified rank or set of ranks within its hierarchy.
-
C.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
D.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
E.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 28, 2026, 7:53 p.m.