Triple
T36282318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEP |
E892971
|
entity |
| Predicate | usesPlanningModel |
P33328
|
FINISHED |
| Object | central planning |
—
|
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: central planning | Statement: [MEP, usesPlanningModel, central planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlanningModel Context triple: [MEP, usesPlanningModel, central planning]
-
A.
planningModelFor
chosen
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
B.
usedPlanningSystem
Indicates that an entity employed a particular planning system or methodology to carry out its planning activities.
-
C.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
D.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
E.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:09 p.m.