Triple
T22752491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3 Crucis |
E562740
|
entity |
| Predicate | flagAppearsOn |
P64836
|
FINISHED |
| Object | flag of Australia |
—
|
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: flag of Australia | Statement: [3 Crucis, flagAppearsOn, flag of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagAppearsOn Context triple: [3 Crucis, flagAppearsOn, flag of Australia]
-
A.
isOnFlagOf
chosen
Indicates that something (typically a symbol, image, or design element) appears on or is depicted on a flag.
-
B.
flagElement
Indicates that one entity serves as a flag or marker element associated with another entity, typically used to signal a condition, state, or special handling.
-
C.
flagshipShowOf
Indicates that one show serves as the primary, most prominent, or representative program associated with a particular entity (such as a network, brand, or organization).
-
D.
flagUsedBy
Indicates that a particular flag is officially used by a specified entity, such as a country, organization, or group.
-
E.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179baa85881909140f41f2428cc98 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.