Triple
T34230804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor General of New York |
E878184
|
entity |
| Predicate | positionAbolishedIn |
P30300
|
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: [Surveyor General of New York, positionAbolishedIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionAbolishedIn Context triple: [Surveyor General of New York, positionAbolishedIn, 19th century]
-
A.
postAbolished
Indicates that a particular official position, office, or post has been formally discontinued and no longer exists.
-
B.
previouslyAbolished
Indicates that something was officially ended, discontinued, or annulled at some point in the past.
-
C.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
-
D.
abolishedDuring
chosen
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
E.
positionOnReform
Indicates a stance or viewpoint that an entity holds regarding a particular reform or set of reforms.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:56 a.m.