Triple
T34949498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanpa |
E1007948
|
entity |
| Predicate | layoutPlanStatus |
P24929
|
FINISHED |
| Object | endorsed |
—
|
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: endorsed | Statement: [Kanpa, layoutPlanStatus, endorsed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutPlanStatus Context triple: [Kanpa, layoutPlanStatus, endorsed]
-
A.
hasPlanningStatus
chosen
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
B.
urbanPlanApproved
Indicates that an official authority has reviewed and formally authorized a proposed urban development or land-use plan.
-
C.
structureStatus
Indicates the current condition or state of completion of a structure in relation to its intended design or function.
-
D.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
E.
planningControl
Indicates that an authority or agent exercises regulatory oversight or decision-making power over how something is planned, developed, or used.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782ccb1ec8190a15e00c9e678e5da |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.