Triple
T22695590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Si(Li) detector |
E561163
|
entity |
| Predicate | hasDepletionDepth |
P36777
|
FINISHED |
| Object | on the order of a few millimeters |
—
|
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: on the order of a few millimeters | Statement: [Si(Li) detector, hasDepletionDepth, on the order of a few millimeters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepletionDepth Context triple: [Si(Li) detector, hasDepletionDepth, on the order of a few millimeters]
-
A.
hasDepth
chosen
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
B.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
C.
isDeepest
Indicates that one entity has the greatest depth relative to a specified reference or set of comparable entities.
-
D.
hasChannelDepth
Indicates that one entity specifies or records the depth measurement of a channel associated with another entity.
-
E.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789e05d88190b9d51bb3f8e3e9d4 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.