Triple
T4460908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Women’s Cross Country Championships |
E98250
|
entity |
| Predicate | displacementRunnersPerTeam |
P39863
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [NCAA Division I Women’s Cross Country Championships, displacementRunnersPerTeam, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementRunnersPerTeam Context triple: [NCAA Division I Women’s Cross Country Championships, displacementRunnersPerTeam, 2]
-
A.
rebootNumberOfTeams
Indicates the number of teams involved in or affected by a particular reboot event or process.
-
B.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
C.
game4CombinedRuns
Indicates the total number of runs scored by both teams combined in the fourth game of a series or set.
-
D.
baseRunners
Indicates that certain players are currently occupying one or more bases as runners in a baseball play or game situation.
-
E.
usesNumberOfPlayersOnFieldPerTeam
chosen
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.