Triple
T10347560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 Major League Soccer season |
E243789
|
entity |
| Predicate | pointForDraw |
P93807
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2001 Major League Soccer season, pointForDraw, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointForDraw Context triple: [2001 Major League Soccer season, pointForDraw, 1]
-
A.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
B.
usesPointsForDraw
Indicates that an entity relies on or applies a points-based system to determine or execute a draw (such as a lottery, selection, or outcome).
-
C.
KPoint
Indicates a relationship where a specific point is designated or identified as a key or reference point within a spatial or geometric context.
-
D.
isPointWhere
Indicates that one entity is the specific location or point at which another entity, event, or condition occurs or is defined.
-
E.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9251654819080d1e3f0ed4ee9d3 |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:56 a.m.