Triple
T10160589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newbury bypass |
E233878
|
entity |
| Predicate | protestPeriod |
P28865
|
FINISHED |
| Object | 1995–1996 |
—
|
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: 1995–1996 | Statement: [Newbury bypass, protestPeriod, 1995–1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protestPeriod Context triple: [Newbury bypass, protestPeriod, 1995–1996]
-
A.
protests
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
B.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
C.
hasProtestMovement
Indicates that an entity is associated with, or gives rise to, an organized protest movement opposing or advocating change related to it.
-
D.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
E.
oppositionPeriodStart
Indicates the point in time when a formal opposition or challenge against something begins.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5831e481909b48fdfa8f1c670b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.