Triple
T19919132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the Empire of Brazil |
E478741
|
entity |
| Predicate | chargeShape |
P71133
|
FINISHED |
| Object | yellow rhombus |
—
|
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: yellow rhombus | Statement: [Flag of the Empire of Brazil, chargeShape, yellow rhombus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeShape Context triple: [Flag of the Empire of Brazil, chargeShape, yellow rhombus]
-
A.
shapeOfCharges
chosen
Indicates the geometric form or configuration that the charges collectively take.
-
B.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
-
C.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
D.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
E.
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.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c3d990819089386d9f30323e8c |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.