Triple

T30345321
Position Surface form Disambiguated ID Type / Status
Subject ALfheim Online E771853 entity
Predicate hasMainHubLocation P104352 FINISHED
Object Alne NE NERFINISHED

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: Alne | Statement: [ALfheim Online, hasMainHubLocation, Alne]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMainHubLocation
Context triple: [ALfheim Online, hasMainHubLocation, Alne]
  • A. hasMainLocationType
    Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
  • B. hasMajorHubIn chosen
    Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
  • C. hasMainHubThroughSubsidiary
    Indicates that an entity’s primary hub or central location is established or operated indirectly through one or more of its subsidiary entities.
  • D. isMajorHubInCountry
    Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
  • E. isRegionalHubOn
    Indicates that an entity functions as a primary regional hub or central node located on or served by a specified network, route, or infrastructure.
  • 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_69f2248b9a208190bc3e6804acd5afd6 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff965f9be48190b015b788207be676 completed May 9, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69ff95d3015c8190b9d293fe31b859c3 completed May 9, 2026, 8:15 p.m.
Created at: April 29, 2026, 7:55 p.m.