Triple
T32073459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force de frappe |
E819077
|
entity |
| Predicate | airBasedComponent |
P41564
|
FINISHED |
| Object | Forces aériennes stratégiques |
—
|
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: Forces aériennes stratégiques | Statement: [Force de frappe, airBasedComponent, Forces aériennes stratégiques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airBasedComponent Context triple: [Force de frappe, airBasedComponent, Forces aériennes stratégiques]
-
A.
airService
Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
-
B.
airborneComponent
Indicates that one entity is a component or part of another entity specifically when that other entity is in an airborne state.
-
C.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
D.
airshipBase
Indicates that one entity serves as the base, home, or primary operating location for an airship or group of airships.
-
E.
hasAirComponent
chosen
Indicates that something includes, contains, or is associated with an air-related component or element.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b52a053c8190ae0898cb78b76688 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:23 a.m.