Triple
T27134612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ångström |
E681647
|
entity |
| Predicate | conversionFactorToMetre |
P88269
|
FINISHED |
| Object | 1e-10 |
—
|
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: 1e-10 | Statement: [ångström, conversionFactorToMetre, 1e-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionFactorToMetre Context triple: [ångström, conversionFactorToMetre, 1e-10]
-
A.
conversionToSIApprox
chosen
Indicates an approximate numerical conversion factor or expression that relates a given quantity or unit to its corresponding value in the International System of Units (SI).
-
B.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
C.
metre
Indicates a measurement relationship where one entity’s length, distance, or size is quantified in units of metres.
-
D.
convertedUnit
Indicates that one unit is the result of converting a quantity expressed in another unit.
-
E.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:06 a.m.