Triple
T36721920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont-Rouge |
E907087
|
entity |
| Predicate | isInCensusSubdivisionType |
P80271
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [Pont-Rouge, isInCensusSubdivisionType, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCensusSubdivisionType Context triple: [Pont-Rouge, isInCensusSubdivisionType, city]
-
A.
isInCensusSubdivision
chosen
Indicates that one entity is located within, or falls under the jurisdiction of, a specific census subdivision.
-
B.
hasCensusSubdivision
Indicates that an entity (typically a larger administrative area) includes or is associated with a specific census-defined subdivision within it.
-
C.
censusSubdivisionType
Indicates the specific administrative or geographic category assigned to a census subdivision (e.g., city, town, rural area) within a census system.
-
D.
isInCensusDivision
Indicates that one entity (typically a geographic area or administrative unit) belongs to or is contained within a specified census division.
-
E.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.