Triple
T27134864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESCA |
E681654
|
entity |
| Predicate | typicalAnalysisDepth |
P200336
|
FINISHED |
| Object | a few nanometers |
—
|
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: a few nanometers | Statement: [ESCA, typicalAnalysisDepth, a few nanometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAnalysisDepth Context triple: [ESCA, typicalAnalysisDepth, a few nanometers]
-
A.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
B.
typicalFormationDepth
Indicates the usual or characteristic depth at which something is formed or occurs within a medium or environment.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalDynamicLevel
Indicates the usual or characteristic intensity or volume level at which an action, event, or interaction typically occurs.
-
E.
searchDepth
Indicates the extent or level to which a search process explores through layers, steps, or hierarchy within a structure or space.
- 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_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: April 27, 2026, 9:06 a.m.