Triple
T3699455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesotho loti |
E78540
|
entity |
| Predicate | legalStatusOfRandInLesotho |
P2250
|
FINISHED |
| Object | legal tender |
—
|
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: legal tender | Statement: [Lesotho loti, legalStatusOfRandInLesotho, legal tender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfRandInLesotho Context triple: [Lesotho loti, legalStatusOfRandInLesotho, legal tender]
-
A.
legalStatusVariesBy
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
B.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
C.
legalStatusModern
Indicates the current legal standing or classification of an entity under contemporary law or regulatory frameworks.
-
D.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
legalStatusAtArrival
Indicates the legal status or classification an entity held at the time it first arrived at a particular place or jurisdiction.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc513d26c8190bfdf25f62af8c6ca |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.