Triple
T32080401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XIII |
E819276
|
entity |
| Predicate | decimalEquivalent |
P7632
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [XIII, decimalEquivalent, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decimalEquivalent Context triple: [XIII, decimalEquivalent, 13]
-
A.
decimalized
chosen
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.
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.
-
C.
conversionDetails
Indicates the specific parameters, conditions, and outcomes associated with transforming one entity, state, or value into another.
-
D.
divisionRepresentation
Indicates a relationship where one entity serves as a symbolic, visual, or structural representation of a division or partition of another entity.
-
E.
expressedInText
Indicates that a particular idea, statement, or piece of information is explicitly conveyed within a given text.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b57e8f608190bf96e5dadf066134 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.