Triple

T27134946
Position Surface form Disambiguated ID Type / Status
Subject ESCA E681655 entity
Predicate canMap P163473 FINISHED
Object lateral distribution of elements on surfaces 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: lateral distribution of elements on surfaces | Statement: [ESCA, canMap, lateral distribution of elements on surfaces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canMap
Context triple: [ESCA, canMap, lateral distribution of elements on surfaces]
  • A. mapsFrom
    Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
  • B. mapsTo
    Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
  • C. mapsAs
    Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
  • D. mappingBy
    Indicates that one entity is related to another through a defined mapping or association, specifying which side or field governs the relationship.
  • E. hasMaps
    Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
  • 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_69eefacbcc2081909ebf00daa23f1981 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f638d11c988190af7fd4572b08e038 completed May 2, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69f63709e4848190b5cf322e06b23fb6 completed May 2, 2026, 5:40 p.m.
PDg Predicate description generation batch_69f638344b148190bf0414ef7c5f1f38 completed May 2, 2026, 5:45 p.m.
Created at: April 27, 2026, 9:06 a.m.