Triple

T37872297
Position Surface form Disambiguated ID Type / Status
Subject The Wandering Isle E944635 entity
Predicate cannotReturnAfterLeaving P192739 FINISHED
Object true 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: true | Statement: [The Wandering Isle, cannotReturnAfterLeaving, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cannotReturnAfterLeaving
Context triple: [The Wandering Isle, cannotReturnAfterLeaving, true]
  • A. mustLeave
    Indicates that an entity is required or compelled to depart from a place, situation, or state.
  • B. reentryProtection
    Indicates that an entity is safeguarded against harmful effects or risks associated with reentering a system, environment, or jurisdiction.
  • C. doesNotEnter
    Indicates that one entity refrains from or fails to go into or cross the boundary of another entity or location.
  • D. cannotExceed
    Indicates that one quantity, value, or limit must not be greater than another specified quantity or threshold.
  • E. forcedToReturnTo
    Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
  • 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_69f76eef55d481908ca6660b4b532550 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd2839880c819099a7a89783f2270e completed May 8, 2026, 12:03 a.m.
PD Predicate disambiguation batch_69fd23dc5da48190ae8ba08947d34956 completed May 7, 2026, 11:44 p.m.
PDg Predicate description generation batch_69fd28379d2c8190903ba228ee1cc756 completed May 8, 2026, 12:03 a.m.
Created at: May 3, 2026, 4:19 p.m.