Triple
T30634651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Kid |
E779804
|
entity |
| Predicate | typicalCompanion |
P22642
|
FINISHED |
| Object | Pancho |
E310383
|
NE 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: Pancho | Statement: [Cisco Kid, typicalCompanion, Pancho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCompanion Context triple: [Cisco Kid, typicalCompanion, Pancho]
-
A.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
typicalComplement
Indicates that one entity serves as the usual or characteristic complement of another, completing or specifying it in a typical or canonical way.
-
C.
typicalBlendPartner
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
-
D.
companionsCategory
Indicates that one entity is classified under a specific category related to companions or companionship.
-
E.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
- F. None of above.
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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2863f2781881909d46eb10efca015e |
completed | June 9, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:28 p.m.