Triple
T909190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Helena pound |
E19618
|
entity |
| Predicate | sameValueAs |
P7398
|
FINISHED |
| Object | British pound sterling at par |
—
|
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: British pound sterling at par | Statement: [Saint Helena pound, sameValueAs, British pound sterling at par]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sameValueAs Context triple: [Saint Helena pound, sameValueAs, British pound sterling at par]
-
A.
hasEquivalent
chosen
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
B.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
D.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
E.
hasExactValue
Indicates that an entity possesses a specific, precisely defined value that must match exactly, without any deviation or tolerance.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.