Triple
T1165555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livingston |
E24590
|
entity |
| Predicate | isPlannedAs |
P11255
|
FINISHED |
| Object | post-war new town |
—
|
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: post-war new town | Statement: [Livingston, isPlannedAs, post-war new town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedAs Context triple: [Livingston, isPlannedAs, post-war new town]
-
A.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
B.
planned
chosen
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
C.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
D.
hasPlannedInstitution
Indicates that an entity has an associated institution that is intended or scheduled to be established or implemented in the future.
-
E.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.