Triple
T21606810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Leones |
E533195
|
entity |
| Predicate | usedInMediaHeadlines |
P144764
|
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: [Los Leones, usedInMediaHeadlines, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMediaHeadlines Context triple: [Los Leones, usedInMediaHeadlines, yes]
-
A.
usedInHeadlinesAbout
Indicates that something (such as a term, phrase, or name) is commonly employed within the headlines of news articles or similar media coverage about a particular subject or entity.
-
B.
usedInMediaOf
Indicates that something (e.g., a work, element, or content) is employed or appears within a particular media work or production.
-
C.
usedInMediaAs
Indicates that something is employed, featured, or referenced within a media work (such as a film, show, game, or publication) in some capacity.
-
D.
commonlyUsedInMediaOf
Indicates that something is frequently employed or featured within a particular medium or type of media.
-
E.
usedByMediaIn
Indicates that something is employed or utilized within a particular media work or medium.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e5783481909db36c388f3ae227 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:33 p.m.