Triple
T26564371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | henry (unit) |
E666335
|
entity |
| Predicate | relatedToQuantity |
P105005
|
FINISHED |
| Object | magnetic flux linkage |
—
|
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: magnetic flux linkage | Statement: [henry (unit), relatedToQuantity, magnetic flux linkage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToQuantity Context triple: [henry (unit), relatedToQuantity, magnetic flux linkage]
-
A.
relatesToQuantity
chosen
Indicates a relationship where one entity is associated with, depends on, or is characterized by a specific quantity or amount.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
D.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
E.
relatedToSpecification
Indicates that something has a connection or relevance to a particular specification, standard, or set of defined requirements.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 27, 2026, 1:54 a.m.