Triple
T37297683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Prussian Jagdstaffel 11 |
E925847
|
entity |
| Predicate | nicknameOfFormation |
P187980
|
FINISHED |
| Object | Flying Circus |
—
|
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: Flying Circus | Statement: [Royal Prussian Jagdstaffel 11, nicknameOfFormation, Flying Circus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfFormation Context triple: [Royal Prussian Jagdstaffel 11, nicknameOfFormation, Flying Circus]
-
A.
monthOfFormation
Indicates the specific calendar month in which an entity (such as an organization or group) was formally established or created.
-
B.
namesakeFounded
Indicates that an entity was founded by a person or organization for whom it is named (i.e., its namesake is also its founder).
-
C.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.