Triple
T102312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Football League |
E2064
|
entity |
| Predicate | playerSource |
P409
|
FINISHED |
| Object | college 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: college football | Statement: [National Football League, playerSource, college football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerSource Context triple: [National Football League, playerSource, college football]
-
A.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
soundCarrier
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
C.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
D.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
E.
discPosition
Indicates the spatial or ordinal placement of a disc relative to a reference point or within a set or structure.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2563a6ff48190bec582fb2f99b7af |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.