Triple
T34185495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamal Jeffries |
E876946
|
entity |
| Predicate | leagueInFiction |
P129655
|
FINISHED |
| Object | fictional professional basketball league |
—
|
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: fictional professional basketball league | Statement: [Jamal Jeffries, leagueInFiction, fictional professional basketball league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueInFiction Context triple: [Jamal Jeffries, leagueInFiction, fictional professional basketball league]
-
A.
fictionalLeague
chosen
Indicates that an entity is associated with or belongs to a league that exists only in fiction rather than in reality.
-
B.
leagueOfFictionalTeam
Indicates that a fictional sports team is a member of, or competes within, a particular sports league.
-
C.
featuresFictionalSport
Indicates that a work includes or showcases a fictional sport as part of its content or setting.
-
D.
portraysFictionalTeam
Indicates that one entity depicts or represents a fictional team within a work or medium.
-
E.
fictionalTeam
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:55 a.m.