Triple
T21262365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk, Virginia |
E524036
|
entity |
| Predicate | dateOfConsolidation |
P21874
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Suffolk, Virginia, dateOfConsolidation, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfConsolidation Context triple: [Suffolk, Virginia, dateOfConsolidation, 1974]
-
A.
consolidationDate
chosen
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
B.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
timeOfMergerOrAcquisition
Indicates the specific point in time when a merger or acquisition event occurs between entities.
-
D.
consolidationOccursDuring
Indicates that a consolidation process takes place within, or is temporally contained by, a specified time period or event.
-
E.
mergerYear
Indicates the year in which two or more entities formally merged into a single entity.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e899e081909d3c98fb12a8b476 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 4 p.m.