Triple
T30923485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brabantine stuiver |
E787791
|
entity |
| Predicate | currencySubdivisionOf |
P39839
|
FINISHED |
| Object | Brabantine guilder |
—
|
NE NERFINISHED |
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: Brabantine guilder | Statement: [Brabantine stuiver, currencySubdivisionOf, Brabantine guilder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencySubdivisionOf Context triple: [Brabantine stuiver, currencySubdivisionOf, Brabantine guilder]
-
A.
currencySubunitOf
chosen
Indicates that a monetary subunit (such as cents) is a fractional unit belonging to and defined in terms of a larger base currency.
-
B.
officialCurrencySubunitOf
Indicates that one unit represents the official fractional subunit (e.g., cents to a dollar) of a specified currency.
-
C.
currencyArea
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
-
D.
ISO4217MinorUnit
Indicates the number of decimal places (minor currency units) used to represent amounts in the currency defined by the ISO 4217 standard.
-
E.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 8:51 p.m.