Triple
T3769405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pfennig |
E82759
|
entity |
| Predicate | valueRelativeToMainUnit |
P51035
|
FINISHED |
| Object | 1/100 |
—
|
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: 1/100 | Statement: [Pfennig, valueRelativeToMainUnit, 1/100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelativeToMainUnit Context triple: [Pfennig, valueRelativeToMainUnit, 1/100]
-
A.
naturalUnitsValue
Indicates that a quantity is expressed in natural units, specifying its value when fundamental physical constants are normalized (e.g., c = ħ = k_B = 1).
-
B.
faceValueUnit
Indicates the unit of measurement in which the face value of something (such as a financial instrument or item) is expressed.
-
C.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
D.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
E.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
- F. None of above. chosen
Provenance (4 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2f016c81909c2e3c85dbc3c259 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.