Triple
T6027696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. C. Nichols |
E134220
|
entity |
| Predicate | usedPlanningTool |
P66532
|
FINISHED |
| Object | restrictive covenants in residential developments |
—
|
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: restrictive covenants in residential developments | Statement: [J. C. Nichols, usedPlanningTool, restrictive covenants in residential developments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPlanningTool Context triple: [J. C. Nichols, usedPlanningTool, restrictive covenants in residential developments]
-
A.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
E.
decisionMakingTool
chosen
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560e3c2c8190aea2619386fc5538 |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.