Triple
T31943685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_cs |
E815590
|
entity |
| Predicate | hasMagnitudeApproximately |
P9773
|
FINISHED |
| Object | 0.973 |
—
|
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.973 | Statement: [V_cs, hasMagnitudeApproximately, 0.973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagnitudeApproximately Context triple: [V_cs, hasMagnitudeApproximately, 0.973]
-
A.
representsApproximately
Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
-
B.
hasApproximateValue
chosen
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.
-
C.
hasMagnitudeProperty
Indicates that an entity is associated with a quantitative magnitude-related property, such as size, intensity, or amount.
-
D.
containsApproximately
Indicates that one entity holds or includes another entity in a quantity or proportion that is close to, but not exactly, a specified amount.
-
E.
alignedApproximately
Indicates that two or more entities are positioned or oriented in roughly the same direction or arrangement, allowing for minor deviations or imprecision.
- 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_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 1, 2026, 12:06 a.m.