Triple
T24029170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Cool |
E595046
|
entity |
| Predicate | hasHonorificSense |
P6819
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Captain Cool, hasHonorificSense, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorificSense Context triple: [Captain Cool, hasHonorificSense, yes]
-
A.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address to another entity.
-
B.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
C.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
D.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
E.
hasHonorificName
chosen
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
- 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.