Triple
T31976824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strike and Return |
E816472
|
entity |
| Predicate | mottoOfUnit |
P163438
|
FINISHED |
| Object | No. 4 Squadron |
—
|
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: No. 4 Squadron | Statement: [Strike and Return, mottoOfUnit, No. 4 Squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOfUnit Context triple: [Strike and Return, mottoOfUnit, No. 4 Squadron]
-
A.
mottoOfRegiment
chosen
Indicates that a particular phrase or motto is officially associated with and represents a specific military regiment.
-
B.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
C.
regimentalMottoTranslation
Indicates the translated wording or meaning of a regiment’s official motto in another language.
-
D.
parentRegimentMotto
Indicates that one regiment’s motto is derived from, associated with, or officially linked to the motto of its parent regiment.
-
E.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:11 a.m.