Triple
T650279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Air Force roundel |
E11330
|
entity |
| Predicate | appliesToBranch |
P3304
|
FINISHED |
| Object | air forces |
—
|
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: air forces | Statement: [French Air Force roundel, appliesToBranch, air forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToBranch Context triple: [French Air Force roundel, appliesToBranch, air forces]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
usedByBranch
chosen
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
C.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
D.
involvedBranch
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
E.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f31e70c81909a2ac1d939f7ec07 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.