Triple
T15640942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman numeral system |
E376061
|
entity |
| Predicate | baseValueOfSymbol |
P57926
|
FINISHED |
| Object | I = 1 |
—
|
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: I = 1 | Statement: [Roman numeral system, baseValueOfSymbol, I = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseValueOfSymbol Context triple: [Roman numeral system, baseValueOfSymbol, I = 1]
-
A.
hasSymbolicValue
Indicates that something holds meaning, significance, or representational value beyond its literal or practical function.
-
B.
symbolForConstant
chosen
Indicates that one entity serves as the symbolic representation or notation used to denote a particular constant.
-
C.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
D.
definesSymbol
Indicates that one entity specifies or establishes another entity as a symbol representing some concept, value, or object.
-
E.
secondSymbolValue
Indicates that the value or quantity associated with the second symbol in a pair or sequence is being specified or referenced.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed06b388190bfebb77fe70e7df1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.