Triple
T7151598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI |
E166702
|
entity |
| Predicate | hasPrefixSystem |
P66954
|
FINISHED |
| Object | decimal prefixes |
—
|
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: decimal prefixes | Statement: [SI, hasPrefixSystem, decimal prefixes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefixSystem Context triple: [SI, hasPrefixSystem, decimal prefixes]
-
A.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
hasPrecedenceSystem
Indicates that one system is defined as having priority or a higher order of precedence over another system in determining outcomes or rules.
-
C.
isInSystem
Indicates that one entity is located within, belongs to, or is contained by a particular system.
-
D.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
E.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f3e4a88190a3110f2368262528 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.