Triple
T1293715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Street (Dallas) |
E27604
|
entity |
| Predicate | dateOfEventProximity |
P830
|
FINISHED |
| Object | 1963-11-22 |
—
|
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: 1963-11-22 | Statement: [Houston Street (Dallas), dateOfEventProximity, 1963-11-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEventProximity Context triple: [Houston Street (Dallas), dateOfEventProximity, 1963-11-22]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
C.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
-
D.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
E.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.