Triple
T25371649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swazi lilangeni |
E632945
|
entity |
| Predicate | pluralSymbol |
P158246
|
FINISHED |
| Object | E |
—
|
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: E | Statement: [Swazi lilangeni, pluralSymbol, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pluralSymbol Context triple: [Swazi lilangeni, pluralSymbol, E]
-
A.
pluralMasculineForm
Indicates that the referenced term is expressed in its plural form specifically for masculine grammatical gender.
-
B.
pluralityJoinedBy
Indicates that multiple entities are combined or grouped together into a single plural unit, typically linked by a coordinating connector (such as "and").
-
C.
postnominalForm
Indicates that one element appears in a position immediately following a noun, typically as a modifier or descriptive form placed after the noun it relates to.
-
D.
singularName
Indicates that an entity has a single-item or singular form of its name used to refer to one instance of that entity.
-
E.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11323e08190a8ec4687f8fefe7f |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:38 p.m.