Triple
T27134897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESCA |
E681654
|
entity |
| Predicate | surfaceSensitivityReason |
P161887
|
FINISHED |
| Object | limited escape depth of photoelectrons |
—
|
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: limited escape depth of photoelectrons | Statement: [ESCA, surfaceSensitivityReason, limited escape depth of photoelectrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceSensitivityReason Context triple: [ESCA, surfaceSensitivityReason, limited escape depth of photoelectrons]
-
A.
isSurfaceSensitive
chosen
Indicates that the property, behavior, or measurement depends strongly on the characteristics or condition of a surface rather than the bulk material.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
-
D.
surfaceStatus
Indicates the condition or state of a surface, such as whether it is intact, damaged, altered, or otherwise characterized.
-
E.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:06 a.m.