Triple
T68920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC |
E1377
|
entity |
| Predicate | leagueTier |
P1906
|
FINISHED |
| Object | top level |
—
|
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: top level | Statement: [NFC, leagueTier, top level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueTier Context triple: [NFC, leagueTier, top level]
-
A.
athleticAssociationTier
chosen
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
-
B.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
-
C.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive league.
-
D.
leagueManaged
Indicates that a league has administrative or organizational control over another entity, such as a team, event, or competition.
-
E.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea8cfd081908a26edad2473dde3 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.