Triple
T19053407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coeymans, New York |
E466323
|
entity |
| Predicate | hasNamedEntityType |
P12498
|
FINISHED |
| Object | geopolitical entity |
—
|
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: geopolitical entity | Statement: [Coeymans, New York, hasNamedEntityType, geopolitical entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedEntityType Context triple: [Coeymans, New York, hasNamedEntityType, geopolitical entity]
-
A.
isNamedEntity
chosen
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
B.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
C.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
D.
hasEntity
Indicates that one entity includes, contains, or is associated with another entity as part of its composition or context.
-
E.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc03dfa08190924a1b8073364fa1 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.