Triple
T6250617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelo v. City of New London |
E140035
|
entity |
| Predicate | purposeOfTaking |
P79
|
FINISHED |
| Object | economic development |
—
|
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: economic development | Statement: [Kelo v. City of New London, purposeOfTaking, economic development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfTaking Context triple: [Kelo v. City of New London, purposeOfTaking, economic development]
-
A.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
C.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
D.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633dde348190bbf02a943d94e3be |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.