Triple
T34539537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool A (2019 Rugby World Cup) |
E886766
|
entity |
| Predicate | hasStandingCriterion |
P200705
|
FINISHED |
| Object | match points |
—
|
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: match points | Statement: [Pool A (2019 Rugby World Cup), hasStandingCriterion, match points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandingCriterion Context triple: [Pool A (2019 Rugby World Cup), hasStandingCriterion, match points]
-
A.
hasQualificationCriteria
Indicates that there are specific conditions or standards that must be met for something to be considered eligible or acceptable.
-
B.
hasStandingCapacity
Indicates that an entity is capable of maintaining or supporting a specified condition, function, or load on an ongoing basis.
-
C.
hasLicenseCriteria
Indicates that an entity is subject to, or must satisfy, specific licensing requirements or conditions.
-
D.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
E.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
| PDg | Predicate description generation | batch_69ffa5f236288190bdad97a41aca3cd8 |
completed | May 9, 2026, 9:24 p.m. |
Created at: May 1, 2026, 2:02 a.m.