Triple
T10703780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breguet Atlantique 2 |
E252346
|
entity |
| Predicate | sensorCapability |
P17581
|
FINISHED |
| Object | surface search radar |
—
|
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: surface search radar | Statement: [Breguet Atlantique 2, sensorCapability, surface search radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorCapability Context triple: [Breguet Atlantique 2, sensorCapability, surface search radar]
-
A.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
displayCapabilities
Indicates the set of functions, features, or behaviors that an entity is able to present or support in a given context.
-
C.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
D.
seekerCapability
chosen
Indicates that an entity has the ability or function to detect, track, or locate a target or object.
-
E.
featuresAbility
Indicates that one entity possesses, includes, or provides a particular ability or capability 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fdddf258819097b9fd26d68cd2e4 |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8ea6408190a800f9cb57372189 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.