Triple
T24306970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Extension |
E612560
|
entity |
| Predicate | finalAbandonmentDate |
P49984
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Pacific Extension, finalAbandonmentDate, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAbandonmentDate Context triple: [Pacific Extension, finalAbandonmentDate, 1980]
-
A.
dateOfAbandonment
chosen
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
-
B.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
C.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
dismissalDate
Indicates the date on which an entity (such as a person, case, or employment) is formally dismissed, terminated, or ended.
-
E.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292272af88190b9c23615adbac911 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:31 a.m.