Triple
T14072471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuskaloosa |
E338643
|
entity |
| Predicate | approximateDateOfEvents |
P877
|
FINISHED |
| Object | 1540 |
—
|
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: 1540 | Statement: [Tuskaloosa, approximateDateOfEvents, 1540]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfEvents Context triple: [Tuskaloosa, approximateDateOfEvents, 1540]
-
A.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
approximateTimeOfDayOfEventCommemorated
Indicates the general time of day during which the commemorated event is understood to have occurred.
-
E.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5aa828819098ef55a70a0decbc |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.