Triple
T33371070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraguayan División Intermedia |
E854491
|
entity |
| Predicate | hasTableCriterion |
P151113
|
FINISHED |
| Object | 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: points | Statement: [Paraguayan División Intermedia, hasTableCriterion, points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTableCriterion Context triple: [Paraguayan División Intermedia, hasTableCriterion, points]
-
A.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
B.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
-
C.
hasOwnTable
Indicates that an entity is associated with or requires a dedicated, separate table (e.g., in a database or data model) rather than sharing one with others.
-
D.
hasTableConfiguration
Indicates that an entity is associated with or defined by a specific arrangement or setup of a table and its properties.
-
E.
hasAssociatedCriteria
chosen
Indicates that one entity is linked to specific criteria that define, constrain, or qualify it.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:35 a.m.