Triple
T35160424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Franklin Broyles |
E1015250
|
entity |
| Predicate | administrativeStart |
P288
|
FINISHED |
| Object | 1974 (athletic director, Arkansas) |
—
|
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: 1974 (athletic director, Arkansas) | Statement: [John Franklin Broyles, administrativeStart, 1974 (athletic director, Arkansas)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStart Context triple: [John Franklin Broyles, administrativeStart, 1974 (athletic director, Arkansas)]
-
A.
administeredOn
Indicates that an action, treatment, or procedure was carried out on a specific date or time.
-
B.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
C.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
administeredUntil
Indicates that an action, treatment, or process was actively administered to an entity up to, but not beyond, a specified end time or date.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:02 p.m.