Triple
T3146657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Games results database |
E65780
|
entity |
| Predicate | containsDataOn |
P18283
|
FINISHED |
| Object | Olympic competition outcomes |
—
|
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: Olympic competition outcomes | Statement: [Olympic Games results database, containsDataOn, Olympic competition outcomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDataOn Context triple: [Olympic Games results database, containsDataOn, Olympic competition outcomes]
-
A.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
B.
containsArticleOn
Indicates that one entity includes or features an article about another entity within its content or collection.
-
C.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
E.
hasContentFrom
Indicates that one entity’s content is derived from, includes, or is based on another entity.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada598ccf08190b8817c456f38f2d7 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.