Triple
T34103200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cap’n Cook |
E874630
|
entity |
| Predicate | statusInElCamino |
P199601
|
FINISHED |
| Object | fugitive |
—
|
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: fugitive | Statement: [Cap’n Cook, statusInElCamino, fugitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInElCamino Context triple: [Cap’n Cook, statusInElCamino, fugitive]
-
A.
statusAfterSedan
Indicates the status or condition of an entity after it has been in a sedan or undergone a sedan-related event or process.
-
B.
statusRelativeToCadillac
Indicates how something is positioned, ranked, or evaluated in comparison to a Cadillac.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
E.
statusInColumbo
Indicates that an entity holds a particular status, role, or condition specifically within the context of Columbo.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 1, 2026, 1:53 a.m.