Triple
T22676434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primera Federación |
E560357
|
entity |
| Predicate | followsPointSystem |
P64949
|
FINISHED |
| Object | three points for a win |
—
|
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: three points for a win | Statement: [Primera Federación, followsPointSystem, three points for a win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPointSystem Context triple: [Primera Federación, followsPointSystem, three points for a win]
-
A.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
B.
gradingSystem
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
-
C.
usesPointsSystem
chosen
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
-
D.
pointsSystemManagedBy
Indicates that the points system is overseen, controlled, or administered by a specified managing entity.
-
E.
raceGradeSystem
Indicates a grading or classification relationship that assigns a performance or quality level to a race or racing event.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785ca1e08190af1a6cdb51ca4fce |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.