Triple
T27825513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Huhne |
E702941
|
entity |
| Predicate | stoodFor |
P163388
|
FINISHED |
| Object | leadership of the Liberal Democrats |
—
|
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: leadership of the Liberal Democrats | Statement: [Chris Huhne, stoodFor, leadership of the Liberal Democrats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoodFor Context triple: [Chris Huhne, stoodFor, leadership of the Liberal Democrats]
-
A.
standsFor
Indicates that one entity represents, symbolizes, or serves as a substitute or abbreviation for another entity.
-
B.
choseToRepresent
Indicates that one entity voluntarily decided to act on behalf of, or serve as a representative for, another entity or cause.
-
C.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
D.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
E.
dissolvedInFavorOf
Indicates that one entity has been formally terminated, annulled, or discontinued in order to benefit, support, or be replaced by another entity.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63895e7b48190857b652d83e0d62a |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:51 p.m.