Triple
T22074405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilip Vengsarkar |
E545486
|
entity |
| Predicate | wasCaptainFrom |
P115062
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Dilip Vengsarkar, wasCaptainFrom, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCaptainFrom Context triple: [Dilip Vengsarkar, wasCaptainFrom, 1987]
-
A.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
B.
formerCaptain
Indicates that an entity once held the role or position of captain but no longer does.
-
C.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
-
D.
servedAsCaptainFrom
chosen
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
E.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.