Triple
T12069900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myriade platform |
E287395
|
entity |
| Predicate | typicalMassRange |
P103038
|
FINISHED |
| Object | around 100–200 kg |
—
|
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: around 100–200 kg | Statement: [Myriade platform, typicalMassRange, around 100–200 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMassRange Context triple: [Myriade platform, typicalMassRange, around 100–200 kg]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
C.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
D.
typicalFermionMass
Indicates the characteristic or representative mass value associated with a given type of fermion.
-
E.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:48 p.m.