Triple
T29229902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic 10 Conference |
E741037
|
entity |
| Predicate | hasChampionshipSport |
P186371
|
FINISHED |
| Object | men's 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: men's soccer | Statement: [Atlantic 10 Conference, hasChampionshipSport, men's soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipSport Context triple: [Atlantic 10 Conference, hasChampionshipSport, men's soccer]
-
A.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
C.
hasSportsRole
Indicates that an entity holds or is assigned a specific role or position within a sports context or organization.
-
D.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
E.
hasTeamsChampionship
Indicates that an entity has won at least one championship title in a teams-based competition or league.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 28, 2026, 12:18 p.m.