Triple
T11077139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Seward |
E261895
|
entity |
| Predicate | recordsEventsVia |
P97078
|
FINISHED |
| Object | phonograph diary |
—
|
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: phonograph diary | Statement: [John Seward, recordsEventsVia, phonograph diary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsEventsVia Context triple: [John Seward, recordsEventsVia, phonograph diary]
-
A.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
B.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
C.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
recordRoute
Indicates that an entity documents or logs the path, sequence, or trajectory taken between locations or states.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7999407288190a901d4a2427a2102 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.