Triple

T9764077
Position Surface form Disambiguated ID Type / Status
Subject Wallacea E236738 entity
Predicate crossedBy P416 FINISHED
Object Lydekker Line E401563 NE 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: Lydekker Line | Statement: [Wallacea, crossedBy, Lydekker Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lydekker Line
Context triple: [Wallacea, crossedBy, Lydekker Line]
  • A. Lydekker Line chosen
    The Lydekker Line is a biogeographical boundary in eastern Indonesia that marks the western limit of Australasian fauna, separating it from the Asian-influenced species to the west.
  • B. Arendal Line
    The Arendal Line is a Norwegian railway route that connects the coastal town of Arendal to the national rail network.
  • C. Solør Line
    Solør Line is a Norwegian railway line running through the Solør district in Innlandet county, historically important for both passenger and freight transport.
  • D. Kongsvinger Line
    The Kongsvinger Line is a Norwegian railway route running east from Oslo toward the Swedish border, serving both passenger and freight traffic.
  • E. Frederiksværk Line
    The Frederiksværk Line is a Danish regional railway line in North Zealand that connects several towns between Hillerød and Hundested.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84d64f6c8190a4ed4e9f5936eda5 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda09ed54c8190a5879e14184cddf4 completed April 1, 2026, 10:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcf2cdd08190a051d406e199f45a completed April 5, 2026, 1:37 a.m.
Created at: March 30, 2026, 8:25 p.m.