Triple
T33135827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syracuse Orange women’s track and field |
E848001
|
entity |
| Predicate | outdoorCompetition |
P176131
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Syracuse Orange women’s track and field, outdoorCompetition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outdoorCompetition Context triple: [Syracuse Orange women’s track and field, outdoorCompetition, yes]
-
A.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
B.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
-
C.
competitionHeld
Indicates that a competitive event takes place or is organized at a particular time and/or location.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
competitionClass
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:27 a.m.