Triple
T20786471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FR-61 |
E511650
|
entity |
| Predicate | hasParentSubdivisionCode |
P50620
|
FINISHED |
| Object | FR |
—
|
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: FR | Statement: [FR-61, hasParentSubdivisionCode, FR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentSubdivisionCode Context triple: [FR-61, hasParentSubdivisionCode, FR]
-
A.
hasParentSubdivisionSet
chosen
Indicates that an entity is associated with a set of higher-level subdivisions to which it belongs or from which it is derived.
-
B.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
C.
hasSubdivisionCodePart
Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
-
D.
hasHigherLevelSubdivisionType
Indicates that one administrative or territorial subdivision type is hierarchically above another within a broader organizational structure.
-
E.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28c0d0c8190aa48e6fdfdaab750 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.