Triple
T33486486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhône Valley urban system |
E857624
|
entity |
| Predicate | hasPlanningRelevanceFor |
P80474
|
FINISHED |
| Object | regional planning in France |
—
|
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: regional planning in France | Statement: [Rhône Valley urban system, hasPlanningRelevanceFor, regional planning in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningRelevanceFor Context triple: [Rhône Valley urban system, hasPlanningRelevanceFor, regional planning in France]
-
A.
hasPlanningSignificance
chosen
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
-
B.
hasPlanningAssociation
Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
-
C.
hasPlanningContext
Indicates that an entity is associated with a specific planning-related situation, scope, or set of conditions that frame how it should be interpreted or used.
-
D.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.