Triple
T643496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tory |
E16790
|
entity |
| Predicate | positionOnReform |
P16872
|
FINISHED |
| Object | cautious about political reform |
—
|
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: cautious about political reform | Statement: [Tory, positionOnReform, cautious about political reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnReform Context triple: [Tory, positionOnReform, cautious about political reform]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionOnReconstruction
Indicates that one entity expresses a stance, opinion, or role regarding the process or policy of reconstruction.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f18216081908331aa12dac40214 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49dc0e6a08190b81d82a6f2571c41 |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.