Triple
T25584633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy Welensky |
E641343
|
entity |
| Predicate | startTimeOfFederationLeadership |
P169893
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Roy Welensky, startTimeOfFederationLeadership, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfFederationLeadership Context triple: [Roy Welensky, startTimeOfFederationLeadership, 1956]
-
A.
startTimeAsPartyLeader
Indicates the point in time at which an entity first assumes the role or position of party leader.
-
B.
startTimeAsCaptain
Indicates the point in time when an entity first assumes the role or position of captain.
-
C.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
D.
executionDateOfLeader
Indicates the date on which a leader was executed.
-
E.
startTimeAsConsort
Indicates the point in time when an individual began serving or being recognized as a consort in relation to 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 21, 2026, 4:15 p.m.