Triple
T21625045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE-RP |
E533678
|
entity |
| Predicate | identifiesCurrentSubdivision |
P145263
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DE-RP, identifiesCurrentSubdivision, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesCurrentSubdivision Context triple: [DE-RP, identifiesCurrentSubdivision, true]
-
A.
representsCurrentSubdivision
Indicates that one entity is the current administrative or organizational subdivision of another entity.
-
B.
isLocatedInSubdivision
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
-
C.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
D.
hasSubdivisionLabel
Indicates that an entity assigns a specific label or name to one of its subdivisions or component parts.
-
E.
isSubdivisionUsedFor
Indicates that a particular subdivision (such as a region, section, or part of something) is utilized for a specified purpose or function.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52121c3c8190b9b4d862ed247c71 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:34 p.m.