Triple
T37898101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Tory |
E945334
|
entity |
| Predicate | spectrumPosition |
P20437
|
FINISHED |
| Object | centre‑right |
—
|
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: centre‑right | Statement: [Blue Tory, spectrumPosition, centre‑right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectrumPosition Context triple: [Blue Tory, spectrumPosition, centre‑right]
-
A.
positionOnSpectrum
chosen
Indicates the relative location or value of something along a defined continuum or range of possible states.
-
B.
spectrum
Indicates a relationship where something is characterized or defined in terms of its position, range, or distribution along a continuous scale or set of varying values.
-
C.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
-
D.
emitsSpectrum
Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
-
E.
spectralProperty
Indicates a relationship where an entity possesses or is characterized by a specific spectral feature, measurement, or behavior (e.g., in its frequency, wavelength, or energy spectrum).
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.