Triple
T3699471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSL |
E78541
|
entity |
| Predicate | usesDecimal |
P6187
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LSL, usesDecimal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDecimal Context triple: [LSL, usesDecimal, true]
-
A.
decimalized
Indicates that something has been converted into or expressed in decimal form, typically changing from another numeral or measurement system to a base-10 representation.
-
B.
isDecimalCurrency
chosen
Indicates that a currency is based on a decimal system, typically using 100 minor units to one major unit.
-
C.
decimalMark
Indicates the symbol or notation used to separate the integer part from the fractional part in a numeral.
-
D.
decimalizationRelatedTo
Indicates a relationship where one entity is connected to the process, consequences, or context of converting a system (typically currency or measurement) to a decimal-based format.
-
E.
numericDecomposition
Indicates that a number is broken down into a set of component numbers or factors whose combination (e.g., sum or product) reconstructs the original value.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc513d26c8190bfdf25f62af8c6ca |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.