Triple
T30817194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gourbesville |
E784812
|
entity |
| Predicate | localLevel |
P49100
|
FINISHED |
| Object | commune |
—
|
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: commune | Statement: [Gourbesville, localLevel, commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localLevel Context triple: [Gourbesville, localLevel, commune]
-
A.
localStatus
Indicates the current condition or state of an entity within a specific local context or environment.
-
B.
territorialLevel
Indicates the administrative or geographic tier at which something is defined, applied, or governed within a territorial hierarchy.
-
C.
cityLevel
Indicates the administrative or hierarchical rank of a city within a broader regional or national structure.
-
D.
hasLocalLevel
chosen
Indicates that one entity possesses, is associated with, or is defined at a specific local administrative or organizational level relative to another entity.
-
E.
localFactorAt
Indicates a relationship where a specific factor or influence is associated with, or applies at, a particular local point, position, or context.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:44 p.m.