Triple
T24013865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tamping iron of Phineas Gage |
E594614
|
entity |
| Predicate | enteredAt |
P154866
|
FINISHED |
| Object | left cheek of Phineas Gage |
—
|
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: left cheek of Phineas Gage | Statement: [tamping iron of Phineas Gage, enteredAt, left cheek of Phineas Gage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredAt Context triple: [tamping iron of Phineas Gage, enteredAt, left cheek of Phineas Gage]
-
A.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
B.
registeredAt
Indicates that an entity has officially enrolled, signed up, or been recorded in a system, organization, or event at a specific place or time.
-
C.
firstEntranceClearedDate
Indicates the date on which an entity’s initial entrance, access, or admission was officially cleared or approved.
-
D.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
E.
enteredBy
Indicates that one entity has been input, recorded, or submitted into a system, record, or context by another entity.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a0aa408190a27fca07777cda05 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:41 p.m.