Triple
T8027463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Worm |
E186890
|
entity |
| Predicate | popularityDomain |
P51715
|
FINISHED |
| Object | professional basketball fandom |
—
|
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: professional basketball fandom | Statement: [The Worm, popularityDomain, professional basketball fandom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityDomain Context triple: [The Worm, popularityDomain, professional basketball fandom]
-
A.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
B.
notableDomain
chosen
Indicates that there is a notable or especially significant association between an entity and a particular domain, field, or area of activity.
-
C.
typicalDomain
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
D.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
E.
domainFocus
Indicates that one entity is the primary topical or subject-matter focus within the conceptual or informational domain defined by 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.