Triple
T26593938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action Area II |
E667435
|
entity |
| Predicate | isPartOfPlanningProject |
P134005
|
FINISHED |
| Object | New Town, Kolkata development project |
—
|
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: New Town, Kolkata development project | Statement: [Action Area II, isPartOfPlanningProject, New Town, Kolkata development project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPlanningProject Context triple: [Action Area II, isPartOfPlanningProject, New Town, Kolkata development project]
-
A.
isOnProject
Indicates that an entity is currently assigned to, involved with, or working on a particular project.
-
B.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
hasPlannedPart
chosen
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 2:09 a.m.