Triple
T28451890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planning Act 2008 |
E716599
|
entity |
| Predicate | decisionMakerOriginal |
P166878
|
FINISHED |
| Object | Infrastructure Planning Commission |
—
|
NE NERFINISHED |
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: Infrastructure Planning Commission | Statement: [Planning Act 2008, decisionMakerOriginal, Infrastructure Planning Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionMakerOriginal Context triple: [Planning Act 2008, decisionMakerOriginal, Infrastructure Planning Commission]
-
A.
decisionMakerType
Indicates the role or category of entity responsible for making a particular decision.
-
B.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
C.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
-
D.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
E.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
- F. None of above. chosen
Provenance (4 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 1:52 a.m.