Triple
T33678903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YJ-83 |
E862838
|
entity |
| Predicate | terminalManeuvers |
P138443
|
FINISHED |
| Object | sea-skimming and evasive maneuvers near target |
—
|
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: sea-skimming and evasive maneuvers near target | Statement: [YJ-83, terminalManeuvers, sea-skimming and evasive maneuvers near target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalManeuvers Context triple: [YJ-83, terminalManeuvers, sea-skimming and evasive maneuvers near target]
-
A.
maneuverType
chosen
Indicates the specific kind or category of maneuver being performed or described in a given context.
-
B.
terminal3Use
Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
-
C.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
-
D.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
E.
terminalSide
Indicates that one entity is located at or forms the end boundary or terminal edge of 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 1:43 a.m.