Triple
T19377303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urbach tail |
E484703
|
entity |
| Predicate | appearsBelow |
P135735
|
FINISHED |
| Object | fundamental absorption edge |
—
|
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: fundamental absorption edge | Statement: [Urbach tail, appearsBelow, fundamental absorption edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsBelow Context triple: [Urbach tail, appearsBelow, fundamental absorption edge]
-
A.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
B.
occursBelow
Indicates that one event or object takes place or is positioned at a lower level or beneath another in a spatial or hierarchical sense.
-
C.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
D.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
E.
mayBeBelow
Indicates that one entity is possibly, but not certainly, positioned lower than another in a spatial or ordered sense.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5cfbf48190ac60e3ffa6baa263 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.