Triple
T32069383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fabulous Hudson Hornet |
E818968
|
entity |
| Predicate | roleInRadiatorSprings |
P201553
|
FINISHED |
| Object | town doctor |
—
|
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: town doctor | Statement: [The Fabulous Hudson Hornet, roleInRadiatorSprings, town doctor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRadiatorSprings Context triple: [The Fabulous Hudson Hornet, roleInRadiatorSprings, town doctor]
-
A.
roleInPlanoReal
Indicates that an entity holds or held a specific role or function within the Plano Real economic plan or initiative.
-
B.
roleAtStrawberryHill
Indicates that an entity holds or held a specific role or position at Strawberry Hill.
-
C.
roleInLyndhurst
Indicates that an entity holds or held a specific role or position within the context of Lyndhurst.
-
D.
serviceAreaRole
Indicates the specific function or responsibility an entity has within a defined service area.
-
E.
facilityRole
Indicates that an entity serves in a particular functional capacity or role within a facility or physical site.
- F. None of above. chosen
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
| PDg | Predicate description generation | batch_6a00045774ec81908ca607565b074f31 |
completed | May 10, 2026, 4:06 a.m. |
Created at: May 1, 2026, 12:23 a.m.