Triple
T8792472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missionary Athletes International |
E209202
|
entity |
| Predicate | usesSport |
P15165
|
FINISHED |
| Object | soccer |
—
|
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: soccer | Statement: [Missionary Athletes International, usesSport, soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSport Context triple: [Missionary Athletes International, usesSport, soccer]
-
A.
usedSportFor
Indicates that an entity employs or utilizes a particular sport as a means, tool, or context for achieving some purpose or performing an activity.
-
B.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
C.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
D.
alsoUsedForSport
Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
-
E.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8f9eb08190bd709f3c8e09412f |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.