Triple
T30924350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pound (unit of currency) |
E787816
|
entity |
| Predicate | hasISOCodeExample |
P189
|
FINISHED |
| Object | GBP |
—
|
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: GBP | Statement: [pound (unit of currency), hasISOCodeExample, GBP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISOCodeExample Context triple: [pound (unit of currency), hasISOCodeExample, GBP]
-
A.
hasISOCode
chosen
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
B.
hasISOCodeType
Indicates that an entity is associated with a specific type or category of ISO code (e.g., country code, currency code, language code).
-
C.
hasISOCodeVariant
Indicates that one entity has an alternative or variant ISO code representation corresponding to another entity.
-
D.
hasISOCodeLevel
Indicates that an entity is associated with a specific level or tier within an ISO (International Organization for Standardization) coding system.
-
E.
haveISO639Code
Indicates that a language or linguistic entity is associated with a specific ISO 639 standardized language code.
- 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_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:51 p.m.