Triple
T27134912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESCA |
E681655
|
entity |
| Predicate | isSurfaceSensitive |
P161887
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ESCA, isSurfaceSensitive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSurfaceSensitive Context triple: [ESCA, isSurfaceSensitive, true]
-
A.
isPressureSensitive
Indicates that an entity responds differently based on the amount or intensity of physical pressure applied to it.
-
B.
hasSurfacePreference
Indicates that an entity tends to favor or is best suited for interacting with a particular type of surface over others.
-
C.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
D.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
E.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62479bbb88190bcad383443cbd638 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:06 a.m.