Triple

T6088088
Position Surface form Disambiguated ID Type / Status
Subject Borexino E135688 entity
Predicate locatedUndergroundDepth P43725 FINISHED
Object approximately 1400 meters of rock 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: approximately 1400 meters of rock | Statement: [Borexino, locatedUndergroundDepth, approximately 1400 meters of rock]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedUndergroundDepth
Context triple: [Borexino, locatedUndergroundDepth, approximately 1400 meters of rock]
  • A. hasUndergroundDepth chosen
    Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
  • B. subterranean
    Indicates that one entity is located beneath the surface of the ground or under another structure or area.
  • C. elevationBelowGround
    Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
  • D. maximumDepthBelowSeaLevel
    Indicates the greatest vertical distance an entity extends or reaches below sea level.
  • E. undergroundBranch
    Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
  • 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_69c0087bcc788190b20f093d3a6c60ec completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c057a6f7588190b265d6005fbaf6b3 completed March 22, 2026, 8:57 p.m.
PD Predicate disambiguation batch_69c049f3b1ec8190bea67a7bec6442a5 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:12 p.m.