Triple
T27134623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ångström |
E681647
|
entity |
| Predicate | typicalBondLengthExample |
P18065
|
FINISHED |
| Object | C–C single bond length is about 1.54 ångströms |
—
|
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: C–C single bond length is about 1.54 ångströms | Statement: [ångström, typicalBondLengthExample, C–C single bond length is about 1.54 ångströms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBondLengthExample Context triple: [ångström, typicalBondLengthExample, C–C single bond length is about 1.54 ångströms]
-
A.
C-C bond length
Indicates the distance between two carbon atoms that are directly bonded to each other in a molecule.
-
B.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
C.
bondsFormed
Indicates that a connection or attachment has been created between two or more entities.
-
D.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
E.
covalentRadiusPm
Indicates the covalent radius of an atom, measured in picometers, representing half the distance between two identical atoms joined by a covalent bond.
- 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_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: April 27, 2026, 9:06 a.m.