Triple
T30556857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machin series |
E777721
|
entity |
| Predicate | hasDenominationRange |
P27293
|
FINISHED |
| Object | low to high face values |
—
|
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: low to high face values | Statement: [Machin series, hasDenominationRange, low to high face values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDenominationRange Context triple: [Machin series, hasDenominationRange, low to high face values]
-
A.
includesDenomination
Indicates that one entity contains, comprises, or explicitly specifies a particular denomination as part of its definition or composition.
-
B.
hasDenominationRole
Indicates that an entity holds or is assigned a specific role or function within a religious denomination or faith organization.
-
C.
coinDenomination
Indicates the specific monetary value assigned to a coin within a currency system.
-
D.
servesDenominations
Indicates that an entity provides services or support to one or more specified denominations.
-
E.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 8:20 p.m.