Triple

T11130081
Position Surface form Disambiguated ID Type / Status
Subject Isla Sorna E263252 entity
Predicate hasFictionalInhabitants P97696 FINISHED
Object cloned dinosaurs 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: cloned dinosaurs | Statement: [Isla Sorna, hasFictionalInhabitants, cloned dinosaurs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalInhabitants
Context triple: [Isla Sorna, hasFictionalInhabitants, cloned dinosaurs]
  • A. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
  • B. hasFictionalEstablishmentType
    Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
  • C. hasFictionalLocation
    Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
  • D. basedInFictionalSetting
    Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
  • E. residesInFictionalLocation
    Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
  • 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_69d6aa9c0ba08190bbd19c217489b755 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e831f4808190afabdaa0e97bbe32 completed April 9, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69d7441efe948190ae4ab020121e169d completed April 9, 2026, 6:15 a.m.
PDg Predicate description generation batch_69d75112eb1c8190ba1dd51e42e8a7e8 completed April 9, 2026, 7:11 a.m.
Created at: April 8, 2026, 9:28 p.m.