Triple
T29157545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microtectonics |
E739091
|
entity |
| Predicate | scaleOfObservation |
P166372
|
FINISHED |
| Object | microscopic scale |
—
|
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: microscopic scale | Statement: [Microtectonics, scaleOfObservation, microscopic scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleOfObservation Context triple: [Microtectonics, scaleOfObservation, microscopic scale]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
C.
plateScale
Indicates the scale factor that converts distances measured on a photographic or detector plate into corresponding angular or physical distances in the observed scene.
-
D.
scaleDefinition
Indicates that an entity specifies the parameters, structure, or measurement system used to define a particular scale.
-
E.
significantScale
Indicates that the scale, size, or magnitude of something is notably large or important relative to a given context or standard.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662aa69d08190b514c85e1c12ed79 |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:46 a.m.