Triple
T6250616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelo v. City of New London |
E140035
|
entity |
| Predicate | involvesTakingOf |
P69329
|
FINISHED |
| Object | privately owned homes |
—
|
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: privately owned homes | Statement: [Kelo v. City of New London, involvesTakingOf, privately owned homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTakingOf Context triple: [Kelo v. City of New London, involvesTakingOf, privately owned homes]
-
A.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
C.
takes
Indicates that one entity receives, accepts, or comes into possession of another entity.
-
D.
takenBy
Indicates that something is captured, acquired, or received by a particular entity.
-
E.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:24 p.m.