Triple
T1286823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian national flag |
E27452
|
entity |
| Predicate | SouthernCrossPosition |
P28081
|
FINISHED |
| Object | fly half of the flag |
—
|
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: fly half of the flag | Statement: [Australian national flag, SouthernCrossPosition, fly half of the flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SouthernCrossPosition Context triple: [Australian national flag, SouthernCrossPosition, fly half of the flag]
-
A.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
B.
liesSoutheastOf
Indicates that one entity is located to the southeast of another, combining both a southern and eastern directional relationship.
-
C.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
- 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_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. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.