Triple
T1196314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micromegas detectors |
E25675
|
entity |
| Predicate | hasAmplificationGapThickness |
P9690
|
FINISHED |
| Object | about 100 micrometers |
—
|
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: about 100 micrometers | Statement: [Micromegas detectors, hasAmplificationGapThickness, about 100 micrometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmplificationGapThickness Context triple: [Micromegas detectors, hasAmplificationGapThickness, about 100 micrometers]
-
A.
thickness
chosen
Indicates the measure of how deep or wide an object or layer is from one surface or side to its opposite.
-
B.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
C.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
D.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
E.
deckArmorThickness
Indicates the thickness of the armor plating on the horizontal deck surface of a vehicle, vessel, or structure.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd7a756c819085d695acfffeaceb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.