Triple
T34591675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woolwich (UK Parliament constituency) |
E888198
|
entity |
| Predicate | wasIndustrialSeat |
P179677
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Woolwich (UK Parliament constituency), wasIndustrialSeat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIndustrialSeat Context triple: [Woolwich (UK Parliament constituency), wasIndustrialSeat, true]
-
A.
hasSeatMaterial
Indicates that an entity’s seat is made of, or covered with, a specified material.
-
B.
seatOrBase
Indicates that one entity serves as the seat, base, or supporting foundation for another entity.
-
C.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
D.
chairIn
Indicates that one entity is a chair located within the spatial bounds or interior of another entity.
-
E.
architectOfSeat
Indicates that an entity serves as the architect responsible for the design of a particular seat (e.g., a legislative seat, position, or designated place).
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.