Triple
T32412501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A'ongote |
E828261
|
entity |
| Predicate | visitedDeerfield |
P16949
|
FINISHED |
| Object | 1741 |
—
|
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: 1741 | Statement: [A'ongote, visitedDeerfield, 1741]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedDeerfield Context triple: [A'ongote, visitedDeerfield, 1741]
-
A.
visitedDuring
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
B.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
C.
visitedWith
Indicates that one entity visited a place or another entity together with a companion entity during the same occasion.
-
D.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
E.
visitedLocation
chosen
Indicates that an entity has gone to or spent time at a particular location.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:53 a.m.