Triple
T4759964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omicron |
E105675
|
entity |
| Predicate | representsQuantity |
P4227
|
FINISHED |
| Object | short o as opposed to long ō |
—
|
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: short o as opposed to long ō | Statement: [Omicron, representsQuantity, short o as opposed to long ō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsQuantity Context triple: [Omicron, representsQuantity, short o as opposed to long ō]
-
A.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
B.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given context.
-
C.
quantifies
chosen
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
D.
quantityType
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
E.
quantifiesOver
Indicates that one entity expresses a quantity, measurement, or numerical specification that applies to or ranges over another entity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.