Triple
T30924390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pound (unit of currency) |
E787816
|
entity |
| Predicate | isCommonlyAbbreviatedAs |
P32259
|
FINISHED |
| Object | £1 for one pound |
—
|
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 for one pound | Statement: [pound (unit of currency), isCommonlyAbbreviatedAs, £1 for one pound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyAbbreviatedAs Context triple: [pound (unit of currency), isCommonlyAbbreviatedAs, £1 for one pound]
-
A.
isCommonAbbreviation
chosen
Indicates that one term is a widely used shortened or abbreviated form of another term.
-
B.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
C.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
D.
abreviaturaFrecuente
Indicates that one term is a common or frequently used abbreviation of another term.
-
E.
usesAbbreviationOf
Indicates that one entity employs a shortened or abbreviated form of the name or designation of 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:51 p.m.