Triple
T27531250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sant’Angelo harbor |
E694977
|
entity |
| Predicate | currencyUsedLocally |
P78277
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [Sant’Angelo harbor, currencyUsedLocally, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyUsedLocally Context triple: [Sant’Angelo harbor, currencyUsedLocally, euro]
-
A.
localCurrency
chosen
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
B.
currencyNameLocal
Indicates the name of a currency as expressed in the local or native language of the region where it is used.
-
C.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
D.
currencyNameLocalScript
Indicates that a currency’s name is given in the local or native writing system of the region where it is used.
-
E.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 1:26 p.m.