Triple
T694947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-3F Sentry |
E13874
|
entity |
| Predicate | radarLocation |
P17562
|
FINISHED |
| Object | rotodome above fuselage |
—
|
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: rotodome above fuselage | Statement: [E-3F Sentry, radarLocation, rotodome above fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarLocation Context triple: [E-3F Sentry, radarLocation, rotodome above fuselage]
-
A.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
B.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
C.
primaryRadar
Indicates that the relationship or action is detected or established using primary radar sensing (i.e., direct reflection of radio waves from a target without requiring a transponder).
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c3f39c8190a3014df428817492 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.