Triple
T31157039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's County |
E794237
|
entity |
| Predicate | abolishedAsOfficialName |
P62748
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Queen's County, abolishedAsOfficialName, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedAsOfficialName Context triple: [Queen's County, abolishedAsOfficialName, 1922]
-
A.
formerOfficialNameOf
chosen
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
B.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
-
C.
abolishedAsSystem
Indicates that something (typically an institution, practice, or system) has been officially ended and no longer exists as an organized or recognized system.
-
D.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
-
E.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:07 p.m.