Triple

T30846136
Position Surface form Disambiguated ID Type / Status
Subject Organ Cave E785637 entity
Predicate hasMappingStatus P143440 FINISHED
Object extensively mapped 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: extensively mapped | Statement: [Organ Cave, hasMappingStatus, extensively mapped]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMappingStatus
Context triple: [Organ Cave, hasMappingStatus, extensively mapped]
  • A. hasOfficialMapping
    Indicates that there exists an established, authoritative correspondence or translation between one entity and another.
  • B. hasMappingProperty
    Indicates that there exists a defined correspondence or association between elements of one set, structure, or representation and elements of another.
  • C. hasExistenceStatus
    Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
  • D. hasMaps
    Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
  • E. hasRepresentationStatus chosen
    Indicates the current state or condition of how something is represented, such as whether its representation exists, is valid, complete, or active.
  • 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_69f224b850848190a4af4ccf8ddadcdf completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69ffde9263248190996f970b6cf6e49d completed May 10, 2026, 1:25 a.m.
PD Predicate disambiguation batch_69ffdd760f1c8190abc6c0c1cd97ba5f completed May 10, 2026, 1:20 a.m.
Created at: April 29, 2026, 8:46 p.m.