Triple
T22732306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan's cavalry |
E562165
|
entity |
| Predicate | leaderRank |
P105228
|
FINISHED |
| Object | brigadier general |
—
|
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: brigadier general | Statement: [Morgan's cavalry, leaderRank, brigadier general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderRank Context triple: [Morgan's cavalry, leaderRank, brigadier general]
-
A.
ledByRank
chosen
Indicates that the leadership of an entity is determined or characterized by a specific rank or hierarchical position.
-
B.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
C.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
D.
partnerRank
Indicates the relative status or level assigned to a partner within a partnership or collaboration hierarchy.
-
E.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792ef5bc819088af71bdc96ed41b |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.