Triple
T14485812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCALP Naval |
E359225
|
entity |
| Predicate | terminalSeekerType |
P114409
|
FINISHED |
| Object | imaging infrared |
—
|
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: imaging infrared | Statement: [SCALP Naval, terminalSeekerType, imaging infrared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalSeekerType Context triple: [SCALP Naval, terminalSeekerType, imaging infrared]
-
A.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
-
C.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
D.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
E.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.