Triple
T31976823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strike and Return |
E816472
|
entity |
| Predicate | mottoOfService |
P42
|
FINISHED |
| Object | Royal Australian Air Force |
—
|
NE NERFINISHED |
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: Royal Australian Air Force | Statement: [Strike and Return, mottoOfService, Royal Australian Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOfService Context triple: [Strike and Return, mottoOfService, Royal Australian Air Force]
-
A.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
B.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
C.
motto
chosen
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
E.
mottoPresent
Indicates that an entity currently has an official motto associated with it.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34570288190985234d65a5de384 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.