Triple
T3921463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi (unit) |
E88967
|
entity |
| Predicate | relatedUnit |
P37
|
FINISHED |
| Object | angstrom |
—
|
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: angstrom | Statement: [Fermi (unit), relatedUnit, angstrom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedUnit Context triple: [Fermi (unit), relatedUnit, angstrom]
-
A.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
B.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
C.
relatedDivision
Indicates that there is an organizational or structural association between two divisions, such as being counterparts, partners, or otherwise linked within a broader entity.
-
D.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
E.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.