Triple
T9804662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer R-99 |
E237923
|
entity |
| Predicate | missionSystems |
P90065
|
FINISHED |
| Object | operator consoles for radar and sensors |
—
|
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: operator consoles for radar and sensors | Statement: [Embraer R-99, missionSystems, operator consoles for radar and sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSystems Context triple: [Embraer R-99, missionSystems, operator consoles for radar and sensors]
-
A.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
missionDesign
Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
-
C.
missionOperator
Indicates that one entity is responsible for operating, managing, or controlling a mission involving another entity.
-
D.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
E.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7a0ce881908f0555d194dece3f |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:29 p.m.