Triple

T6866084
Position Surface form Disambiguated ID Type / Status
Subject Platform 9¾ E158402 entity
Predicate fandomActivity P74196 FINISHED
Object tourist photo location 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: tourist photo location | Statement: [Platform 9¾, fandomActivity, tourist photo location]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fandomActivity
Context triple: [Platform 9¾, fandomActivity, tourist photo location]
  • A. fandomFocus
    Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
  • B. fandomScope
    Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
  • C. fandomType
    Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
  • D. fandomCulture
    Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
  • E. fandomContext
    Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
  • 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_69c68831e3648190a643c328122e4d43 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6da3ce95081909a424ac04bc7fa07 completed March 27, 2026, 7:27 p.m.
PD Predicate disambiguation batch_69c6d7b168908190b2f7c724b1bc7fc9 completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6da3b5510819093c5893ea92ac025 completed March 27, 2026, 7:27 p.m.
Created at: March 27, 2026, 2:21 p.m.