Triple

T9241546
Position Surface form Disambiguated ID Type / Status
Subject Manila–Los Angeles E222069 entity
Predicate crossesInternationalDateLine P17114 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: [Manila–Los Angeles, crossesInternationalDateLine, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossesInternationalDateLine
Context triple: [Manila–Los Angeles, crossesInternationalDateLine, true]
  • A. relativePositionToInternationalDateLine chosen
    Indicates the spatial relationship of an entity’s location with respect to the International Date Line (e.g., whether and how it lies to the east, west, or across it).
  • B. numberOfTimeZonesCrossed
    Indicates the count of distinct time zones that an entity passes through or traverses during a specified journey or process.
  • C. crossingDate
    Indicates the date on which the crossing event between the related entities took place.
  • D. crossesBetween
    Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
  • E. crossesBorderOf
    Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
  • 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_69ca83ee26cc81909ac624e190597d6d completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cd03ea9d90819096f9ca5321dffd56 completed April 1, 2026, 11:39 a.m.
PD Predicate disambiguation batch_69cc7a4765648190aa9445c4a22dc471 completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:30 p.m.