Triple
T31943635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_us |
E815589
|
entity |
| Predicate | hasApproximateMagnitude |
P111021
|
FINISHED |
| Object | 0.224 |
—
|
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: 0.224 | Statement: [V_us, hasApproximateMagnitude, 0.224]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMagnitude Context triple: [V_us, hasApproximateMagnitude, 0.224]
-
A.
hasMagnitudeProperty
Indicates that an entity is associated with a quantitative magnitude-related property, such as size, intensity, or amount.
-
B.
hasEstimatedMagnitude
chosen
Indicates that an entity is associated with an approximate or calculated value representing its magnitude or size.
-
C.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
D.
hasApproximateAbsoluteMagnitude
Indicates that an entity is associated with an estimated value of its absolute magnitude, rather than a precisely measured one.
-
E.
approximateSideLengthOrderOfMagnitude
Indicates that one entity’s side length is approximately the same order of magnitude as another entity’s side length, differing by no more than about a factor of ten.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 12:06 a.m.