Triple

T27760350
Position Surface form Disambiguated ID Type / Status
Subject Neapolitan Yellow Tuff eruption E701449 entity
Predicate hasDepositThickness P9690 FINISHED
Object tens of meters in proximal areas 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: tens of meters in proximal areas | Statement: [Neapolitan Yellow Tuff eruption, hasDepositThickness, tens of meters in proximal areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDepositThickness
Context triple: [Neapolitan Yellow Tuff eruption, hasDepositThickness, tens of meters in proximal areas]
  • A. hasThicknessRange
    Indicates that an entity is associated with a minimum and maximum thickness value defining the range of its thickness.
  • B. hasApproximateAverageThickness
    Indicates that an entity possesses a thickness value that is an estimated or typical average rather than an exact measurement.
  • C. hasMaximumThickness
    Indicates that an entity possesses a specified upper limit on its thickness.
  • D. wallThicknessComparedTo
    Indicates how the thickness of one wall relates to the thickness of another wall, typically in terms of being greater, equal, or less.
  • E. thickness chosen
    Indicates the measure of how deep or wide an object or layer is from one surface or side to its opposite.
  • 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_69ef6a5193808190816eb7d0020b2d87 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f791cc969c8190bf187d6031a030d5 completed May 3, 2026, 6:19 p.m.
PD Predicate disambiguation batch_69f791033d288190b118029fe412b9c9 completed May 3, 2026, 6:16 p.m.
Created at: April 27, 2026, 4:26 p.m.