Triple
T26247858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southampton (village), New York |
E656498
|
entity |
| Predicate | subdivisionType4 |
P163718
|
FINISHED |
| Object | country |
—
|
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: country | Statement: [Southampton (village), New York, subdivisionType4, country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionType4 Context triple: [Southampton (village), New York, subdivisionType4, country]
-
A.
subdivisionType0
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
B.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
C.
subdivisionNameType
Indicates the type or category of a named geographic or administrative subdivision (e.g., province, state, district) associated with an entity.
-
D.
subdivisionStatus
Indicates the current state or phase of a subdivision process or classification for an entity.
-
E.
subdivisionUnitOf
Indicates that one administrative or organizational unit functions as a smaller constituent part within a larger unit.
- F. None of above. chosen
Provenance (4 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 26, 2026, 9:06 p.m.