Triple
T8932268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L$ |
E212684
|
entity |
| Predicate | representsSubunit |
P28620
|
FINISHED |
| Object | 100 cents (of the Liberian dollar) |
—
|
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: 100 cents (of the Liberian dollar) | Statement: [L$, representsSubunit, 100 cents (of the Liberian dollar)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSubunit Context triple: [L$, representsSubunit, 100 cents (of the Liberian dollar)]
-
A.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
B.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
C.
representsSubdivision
Indicates that one entity is a subdivision or smaller administrative/organizational unit within another, larger entity.
-
D.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
E.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668e5c108190b08f9cd6b4fd4a8b |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.