Triple
T11268006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Link |
E266737
|
entity |
| Predicate | currencyOfName |
P98839
|
FINISHED |
| Object | historical project name |
—
|
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: historical project name | Statement: [University Link, currencyOfName, historical project name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyOfName Context triple: [University Link, currencyOfName, historical project name]
-
A.
currencyNickname
Indicates that one term is an informal or colloquial nickname used to refer to a particular currency.
-
B.
currencyNameTransliteration
Indicates the transliterated form of a currency’s name from its original script into another writing system.
-
C.
currencyNameLocalScript
Indicates that a currency’s name is given in the local or native writing system of the region where it is used.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyFamily
Indicates that two currencies belong to the same broader monetary family or classification, typically sharing a common origin, standard, or structural framework.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94f60d48190bc925c3cb88641a8 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.