Triple
T34347080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod AEW3 |
E881463
|
entity |
| Predicate | intendedRadarSupplier |
P173482
|
FINISHED |
| Object | GEC-Marconi |
—
|
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: GEC-Marconi | Statement: [Nimrod AEW3, intendedRadarSupplier, GEC-Marconi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRadarSupplier Context triple: [Nimrod AEW3, intendedRadarSupplier, GEC-Marconi]
-
A.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
B.
radarManufacturer
chosen
Indicates that one entity is the manufacturer or producer of a radar system used or associated with another entity.
-
C.
radarFunction
Indicates that one entity serves as the functional role, purpose, or operational capability of a radar system in relation to another entity.
-
D.
hasRadarServices
Indicates that one entity provides or is equipped with radar-based services or capabilities for another entity or context.
-
E.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 1:58 a.m.