Triple
T6547463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liguilla |
E151045
|
entity |
| Predicate | hasSeedingBasedOn |
P3620
|
FINISHED |
| Object | regular season standings |
—
|
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: regular season standings | Statement: [Liguilla, hasSeedingBasedOn, regular season standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeedingBasedOn Context triple: [Liguilla, hasSeedingBasedOn, regular season standings]
-
A.
hasSeeding
Indicates that an entity is assigned or associated with a specific seeding position or rank, typically for ordering or placement in a competitive or structured context.
-
B.
hasSeed
Indicates that one entity contains, produces, or is characterized by the presence of a seed associated with another entity.
-
C.
usesSeeding
chosen
Indicates that an entity employs a seeding process or strategy to initiate, distribute, or propagate something (such as data, content, or resources).
-
D.
hasSeedingRange
Indicates the range or interval of seed positions or rankings within which something is assigned or considered.
-
E.
hasSeedCount
Indicates that an entity possesses a specific number of seeds.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.