Triple
T18571723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Edwards |
E453888
|
entity |
| Predicate | hasCaptaincyFormat |
P57178
|
FINISHED |
| Object | ODI |
—
|
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: ODI | Statement: [Scott Edwards, hasCaptaincyFormat, ODI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptaincyFormat Context triple: [Scott Edwards, hasCaptaincyFormat, ODI]
-
A.
captaincyFormat
chosen
Indicates the specific structure or style in which a captaincy role or tenure is represented or recorded.
-
B.
captainedFormat
Indicates that one entity served as the captain or leader in charge of another entity, typically a team, vessel, or organized group, during a specific event or period.
-
C.
captaincyStyle
Indicates the manner or approach with which an individual leads or commands a team or group as its captain.
-
D.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
E.
captaincyPrecedes
Indicates that one captaincy role or tenure occurs earlier in time than another captaincy role or tenure.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b021ea4819095fe06be88e74133 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.