Triple
T29094056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton Pavilion |
E734939
|
entity |
| Predicate | firstGreenMP |
P202489
|
FINISHED |
| Object | Caroline Lucas |
—
|
NE NERFINISHED |
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: Caroline Lucas | Statement: [Brighton Pavilion, firstGreenMP, Caroline Lucas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGreenMP Context triple: [Brighton Pavilion, firstGreenMP, Caroline Lucas]
-
A.
firstMSP
Indicates that one entity is the first managed service provider (MSP) associated with, selected by, or responsible for another entity.
-
B.
firstToFeature
Indicates that one entity was the earliest or initial subject to exhibit, include, or present another entity in a given context.
-
C.
firstMPAfterCreation
Indicates that the referenced entity is the first meeting point or milestone that occurs immediately after the creation of a given object or entity.
-
D.
firstIndication
Indicates that something is the earliest or initial sign, symptom, or evidence pointing to a particular condition, event, or state.
-
E.
firstSeries
Indicates that one entity is the initial or earliest series in an ordered sequence of related series.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
| PDg | Predicate description generation | batch_6a008ac2d0dc8190865ccedb2003d0ed |
completed | May 10, 2026, 1:40 p.m. |
Created at: April 28, 2026, 11:07 a.m.