Triple
T6423569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckingham (UK Parliament constituency) |
E128002
|
entity |
| Predicate | representedBySpeaker |
P70795
|
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: [Buckingham (UK Parliament constituency), representedBySpeaker, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedBySpeaker Context triple: [Buckingham (UK Parliament constituency), representedBySpeaker, true]
-
A.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
B.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
representedTo
Indicates that one entity formally acted on behalf of or served as the representative of another entity in a given context or interaction.
-
D.
recognizedAsRepresentativeBy
Indicates that one entity is acknowledged or accepted by another entity as acting as its representative.
-
E.
usedBySpeakers
Indicates that something (such as a resource, tool, or method) is employed or utilized by speakers.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:43 p.m.