Triple
T2811085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAK |
E54170
|
entity |
| Predicate | usedOnWebsites |
P43741
|
FINISHED |
| Object | sports news sites |
—
|
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: sports news sites | Statement: [LAK, usedOnWebsites, sports news sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnWebsites Context triple: [LAK, usedOnWebsites, sports news sites]
-
A.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
alsoUsedOnLine
Indicates that something used in one context, medium, or location is additionally used on a specific line (such as a route, circuit, or sequence).
-
C.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
D.
operatedWebsite
Indicates that one entity runs, manages, or controls the functioning of a particular website.
-
E.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde354a5881908cd3d545f7dda81c |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:59 p.m.