Triple
T31690886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOND |
E808786
|
entity |
| Predicate | symbolForAccelerationScale |
P174111
|
FINISHED |
| Object | a0 |
—
|
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: a0 | Statement: [MOND, symbolForAccelerationScale, a0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForAccelerationScale Context triple: [MOND, symbolForAccelerationScale, a0]
-
A.
symbolForCharacteristicAcceleration
chosen
Indicates that one entity serves as the symbolic representation used to denote the characteristic acceleration associated with another entity.
-
B.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
C.
accelerationStyle
Indicates the manner or pattern in which acceleration is applied or experienced in a given context.
-
D.
accelerationElement
Indicates that one entity is an element or component contributing to the acceleration of another entity or process.
-
E.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:08 p.m.