Triple
T393271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC playoffs |
E8925
|
entity |
| Predicate | usesSeedingBasedOn |
P3620
|
FINISHED |
| Object | regular-season record |
—
|
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 record | Statement: [AFC playoffs, usesSeedingBasedOn, regular-season record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeedingBasedOn Context triple: [AFC playoffs, usesSeedingBasedOn, regular-season record]
-
A.
usesSeeding
chosen
Indicates that an entity employs a seeding process or strategy to initiate, distribute, or propagate something (such as data, content, or resources).
-
B.
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.
-
C.
hasSeedCount
Indicates that an entity possesses a specific number of seeds.
-
D.
seedType
Indicates the specific kind or category of seed associated with an entity.
-
E.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec7637c08190b695ec640edbf6c2 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96a8ca48190abbd8de9b02c115c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.