Triple
T1286829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian national flag |
E27452
|
entity |
| Predicate | designSelectedBy |
P381
|
FINISHED |
| Object | public design competition |
—
|
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: public design competition | Statement: [Australian national flag, designSelectedBy, public design competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSelectedBy Context triple: [Australian national flag, designSelectedBy, public design competition]
-
A.
designSpecifiedBy
Indicates that the design or specification of one entity is defined, authored, or determined by another entity.
-
B.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d1a5508190b4461df77f560df4 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.