Triple
T7263404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League1 Ontario Women’s Championship |
E159710
|
entity |
| Predicate | pyramid |
P25583
|
FINISHED |
| Object | Ontario women’s soccer pyramid |
—
|
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: Ontario women’s soccer pyramid | Statement: [League1 Ontario Women’s Championship, pyramid, Ontario women’s soccer pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pyramid Context triple: [League1 Ontario Women’s Championship, pyramid, Ontario women’s soccer pyramid]
-
A.
pyramidName
Indicates that a pyramid is associated with a specific name or title.
-
B.
pyramidDesignation
Indicates that one entity is formally designated or classified as a pyramid in relation to another entity or context.
-
C.
hasPyramid
chosen
Indicates that one entity possesses, contains, or features a pyramid in relation to another entity.
-
D.
pyramidShape
Indicates that an entity has the geometric form or overall structure of a pyramid.
-
E.
pyramidAngle
Indicates that there is a specified angular relationship between elements (such as faces, edges, or apex and base) of a pyramid-shaped structure.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.