Triple
T24029165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Cool |
E595046
|
entity |
| Predicate | roleOfReferredPerson |
P4342
|
FINISHED |
| Object | wicket-keeper batsman |
—
|
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: wicket-keeper batsman | Statement: [Captain Cool, roleOfReferredPerson, wicket-keeper batsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfReferredPerson Context triple: [Captain Cool, roleOfReferredPerson, wicket-keeper batsman]
-
A.
referralRelationship
Indicates a relationship in which one entity directs or recommends another entity to a third party for services, information, or further action.
-
B.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
C.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
D.
refersToPersonFrom
Indicates that one entity makes reference to, mentions, or is about a person originating from or associated with a particular place or group.
-
E.
referredTo
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76e10fc8190afa60c618a4398ee |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.