Triple
T8305204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evacuation Day (New York) |
E194446
|
entity |
| Predicate | observedInThePast |
P25005
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Evacuation Day (New York), observedInThePast, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInThePast Context triple: [Evacuation Day (New York), observedInThePast, 19th century]
-
A.
dstObservedHistorically
Indicates that something has been observed or recorded at a particular destination or location in the past.
-
B.
previouslyObserved
chosen
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
-
C.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
D.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
E.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8db3a8819083772db5c7a2454b |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.