Triple
T37623037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakland Mills |
E936122
|
entity |
| Predicate | followsPlanningModel |
P58411
|
FINISHED |
| Object | village concept of Columbia |
—
|
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: village concept of Columbia | Statement: [Oakland Mills, followsPlanningModel, village concept of Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPlanningModel Context triple: [Oakland Mills, followsPlanningModel, village concept of Columbia]
-
A.
followsPlanType
Indicates that one entity adheres to, or is carried out according to, a specified type of plan.
-
B.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
C.
hasPlanningPattern
chosen
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
-
D.
hasPlanningAssociation
Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:18 p.m.