Triple
T29413856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Cowdrey |
E745969
|
entity |
| Predicate | captaincyTests |
P167153
|
FINISHED |
| Object | 27 |
—
|
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: 27 | Statement: [Colin Cowdrey, captaincyTests, 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captaincyTests Context triple: [Colin Cowdrey, captaincyTests, 27]
-
A.
captaincyPrecedes
Indicates that one captaincy role or tenure occurs earlier in time than another captaincy role or tenure.
-
B.
captaincyOf
Indicates that one entity holds the role or position of captain for another entity, such as a team, group, or vessel.
-
C.
captaincyTradition
Indicates a customary or historically established practice regarding who holds or assumes the role of captain in a given context.
-
D.
captaincyStyle
Indicates the manner or approach with which an individual leads or commands a team or group as its captain.
-
E.
captaincyAchievement
Indicates the achievement or success attained by an entity specifically in its role as a captain or leader.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3b1e108190bec0049dc39f8926 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:59 p.m.