Triple
T2425292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goleo VI |
E53511
|
entity |
| Predicate | companionType |
P28650
|
FINISHED |
| Object | talking football |
—
|
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: talking football | Statement: [Goleo VI, companionType, talking football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionType Context triple: [Goleo VI, companionType, talking football]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
C.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
D.
companionsCategory
chosen
Indicates that one entity is classified under a specific category related to companions or companionship.
-
E.
hasCompanionBook
Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.