Triple
T34172910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | peso |
E876589
|
entity |
| Predicate | typicalSubdivisionValue |
—
|
GENERATED |
| Object | 100 centavos |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubdivisionValue Context triple: [peso, typicalSubdivisionValue, 100 centavos]
-
A.
hasSubdivisionTypical
Indicates that an entity typically has a particular kind of subdivision as a characteristic or representative part of its structure.
-
B.
typicalSubunitOf
chosen
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
C.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
D.
traditionalSubdivisionOf
Indicates that one entity is a historically or culturally recognized sub-unit or component region of another, according to traditional (rather than strictly modern administrative) divisions.
-
E.
primarySubdivisionOf
Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic entity.
- F. None of above.
Provenance (1 batch)
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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.