Triple
T23476911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Southern Rhodesia |
E570287
|
entity |
| Predicate | fieldCharge |
P152520
|
FINISHED |
| Object | golden miner’s pick |
—
|
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: golden miner’s pick | Statement: [Coat of arms of Southern Rhodesia, fieldCharge, golden miner’s pick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldCharge Context triple: [Coat of arms of Southern Rhodesia, fieldCharge, golden miner’s pick]
-
A.
legalCharge
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
-
B.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
C.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
-
D.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
E.
flyCharge
Indicates that an entity is responsible for paying or incurring a fee associated with a flight.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74cf57081909d2b90a806d68c08 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:01 p.m.