Triple
T4759944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omicron |
E105675
|
entity |
| Predicate | historicalSoundValue |
P58360
|
FINISHED |
| Object | /o/ |
—
|
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: /o/ | Statement: [Omicron, historicalSoundValue, /o/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSoundValue Context triple: [Omicron, historicalSoundValue, /o/]
-
A.
historicalValue
Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
-
B.
historicalGauge
Indicates that one entity serves as a gauge, measure, or reference point for understanding the historical state, level, or condition of another entity.
-
C.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
D.
historicalVolume
Indicates a relationship where a volume (such as a book, record, or dataset) pertains to or documents historical information or events.
-
E.
historicallyMeasuredBy
Indicates that one quantity, property, or phenomenon was traditionally or formerly quantified or assessed using a particular measurement method, unit, or instrument.
- 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_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. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.