Triple
T25550188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Saunders Dundas |
E640416
|
entity |
| Predicate | promotedToCaptainYear |
P92863
|
FINISHED |
| Object | 1830 |
—
|
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: 1830 | Statement: [Richard Saunders Dundas, promotedToCaptainYear, 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToCaptainYear Context triple: [Richard Saunders Dundas, promotedToCaptainYear, 1830]
-
A.
promotedToCaptain
chosen
Indicates that an entity has been elevated in rank or position to the role or status of captain.
-
B.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
C.
yearsAsCaptainEnd
Indicates the point in time or year when an entity’s tenure or period of serving as captain ends.
-
D.
startTimeAsCaptain
Indicates the point in time when an entity first assumes the role or position of captain.
-
E.
teamCaptainStartYear
Indicates the year in which an entity first began serving as the captain of a team.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 3:36 p.m.