Triple
T28369949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonga Plate |
E718597
|
entity |
| Predicate | hasSlab |
P164693
|
FINISHED |
| Object | Tonga slab |
—
|
NE NERFINISHED |
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: Tonga slab | Statement: [Tonga Plate, hasSlab, Tonga slab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlab Context triple: [Tonga Plate, hasSlab, Tonga slab]
-
A.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
hasSluicesAt
Indicates a relationship where a structure or system possesses sluice mechanisms located at a specific place or point.
-
C.
hasMezzanine
Indicates that one entity includes or is equipped with a mezzanine level in relation to another entity.
-
D.
hasStalls
Indicates that an entity contains, provides, or is equipped with stalls (e.g., booths, compartments, or vendor stands).
-
E.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 12:58 a.m.