Triple
T35594621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orgeval |
E1028592
|
entity |
| Predicate | hasLocalPlanning |
P33672
|
FINISHED |
| Object | urban planning regulations |
—
|
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: urban planning regulations | Statement: [Orgeval, hasLocalPlanning, urban planning regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalPlanning Context triple: [Orgeval, hasLocalPlanning, urban planning regulations]
-
A.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
B.
hasPlanner
Indicates that an entity is associated with or assigned a planner responsible for organizing or managing its activities or processes.
-
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.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
E.
hasPlanningLevel
chosen
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:05 p.m.