Triple
T37119558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprague |
E919208
|
entity |
| Predicate | hasCategoryOfBearers |
P34346
|
FINISHED |
| Object | military leaders |
—
|
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: military leaders | Statement: [Sprague, hasCategoryOfBearers, military leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCategoryOfBearers Context triple: [Sprague, hasCategoryOfBearers, military leaders]
-
A.
hasNotableBearersType
Indicates that an entity has notable bearers belonging to a specified type or category.
-
B.
hasNotableFieldOfBearers
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
C.
hasMultipleBearers
Indicates that a single item, attribute, or role is associated with more than one bearer or holder simultaneously.
-
D.
typicalBearers
chosen
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
-
E.
hasNotableBearersCount
Indicates the number of notable individuals or entities that bear or are associated with the subject.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:15 p.m.