Triple
T3962893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belize dollar |
E85944
|
entity |
| Predicate | unitNamePlural |
P53630
|
FINISHED |
| Object | dollars |
—
|
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: dollars | Statement: [Belize dollar, unitNamePlural, dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitNamePlural Context triple: [Belize dollar, unitNamePlural, dollars]
-
A.
subunitNamePlural
Indicates that an entity has multiple subunits and specifies the pluralized name used to refer collectively to those subunits.
-
B.
numberOfUnits
Indicates the quantity or count of discrete units associated with an entity or relationship.
-
C.
unitFractionalName
Indicates that one entity is the name or label used to represent a fractional unit of another entity (such as a measurement or quantity).
-
D.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
E.
commerceClausePluralityBy
Indicates that a particular interpretation or application of the Commerce Clause is supported by a plurality (but not a majority) of decision-makers, such as judges in a court.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefba6b9848190a7b0fb66100a2a0c |
completed | March 9, 2026, 4:56 p.m. |
Created at: March 9, 2026, 3:31 p.m.