Triple
T4465352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuvaluan dollar |
E98363
|
entity |
| Predicate | hasLocalDesigns |
P19107
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tuvaluan dollar, hasLocalDesigns, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalDesigns Context triple: [Tuvaluan dollar, hasLocalDesigns, true]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
usedDomesticDesigns
chosen
Indicates that one entity employed or incorporated designs originating from its own country or local context in relation to another entity or activity.
-
D.
usedForeignDesigns
Indicates that an entity employed or incorporated designs originating from a foreign or external source.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35697937c8190b91f72d9e4f945f6 |
completed | March 13, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.