Triple
T8584303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar Hill |
E203263
|
entity |
| Predicate | hasPlannedCharacter |
P32324
|
FINISHED |
| Object | modern planned village |
—
|
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: modern planned village | Statement: [Bar Hill, hasPlannedCharacter, modern planned village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedCharacter Context triple: [Bar Hill, hasPlannedCharacter, modern planned village]
-
A.
hasPlanningCharacteristic
chosen
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
B.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
C.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
D.
hasGhostCharacter
Indicates that an entity includes, features, or is associated with a character that is a ghost.
-
E.
hasPlanner
Indicates that an entity is associated with or assigned a planner responsible for organizing or managing its activities or processes.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1ecc188190bbe2ab8d2423505b |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.