Triple

T38582810
Position Surface form Disambiguated ID Type / Status
Subject Great Sea E932281 entity
Predicate inUniverseLocationOf P120678 FINISHED
Object various naval factions and fleets 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: various naval factions and fleets | Statement: [Great Sea, inUniverseLocationOf, various naval factions and fleets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseLocationOf
Context triple: [Great Sea, inUniverseLocationOf, various naval factions and fleets]
  • A. inUniverseLocationType
    Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
  • B. hasInUniverseLocationRelation chosen
    Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
  • C. inUniverseRegion
    Indicates that an entity is located within or belongs to a specific universe-defined region or area.
  • D. inUniversePosition
    Indicates the spatial or locational position of an entity within a defined universe or world context.
  • E. inUniverseSystem
    Indicates that one entity exists or operates within the scope, rules, or continuity of a particular fictional or conceptual universe or system.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd91a5dad8819093eeeef527027890 completed May 8, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69fd8f65fe9081908902500a3228d935 completed May 8, 2026, 7:23 a.m.
Created at: May 3, 2026, 4:32 p.m.