Triple
T29235716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P |
E741187
|
entity |
| Predicate | representsSubunitRelationship |
P26378
|
FINISHED |
| Object | 1 pula = 100 thebe |
—
|
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: 1 pula = 100 thebe | Statement: [P, representsSubunitRelationship, 1 pula = 100 thebe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSubunitRelationship Context triple: [P, representsSubunitRelationship, 1 pula = 100 thebe]
-
A.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
B.
introducedAsSubunitOf
Indicates that one entity was presented or established as a subordinate or component part of another entity.
-
C.
submultipleRelation
chosen
Indicates that one quantity is an exact submultiple of another, meaning it divides the other quantity into an integer number of equal parts.
-
D.
replacedSubunitOf
Indicates that one subunit has been substituted for or taken the place of another subunit within a larger structure or system.
-
E.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 12:29 p.m.