Triple
T2863307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fandom |
E63376
|
entity |
| Predicate | hostsContentAbout |
P42786
|
FINISHED |
| Object | entertainment franchises |
—
|
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: entertainment franchises | Statement: [Fandom, hostsContentAbout, entertainment franchises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsContentAbout Context triple: [Fandom, hostsContentAbout, entertainment franchises]
-
A.
hostsBody
Indicates that one entity serves as the physical container or location in which another entity resides or is situated.
-
B.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
C.
mainHostTitle
Indicates the primary title or designation held by the main host in a given context or event.
-
D.
homeSupportersSectionFor
Indicates that a particular seating section is designated for the home team's supporters at a sporting event or venue.
-
E.
homeSectionName
Indicates the designated name or label assigned to a particular section of a home or homepage.
- F. None of above. chosen
Provenance (4 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb6e6988190b832ee05d8420633 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:02 p.m.