Triple
T12717079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-3DR |
E303872
|
entity |
| Predicate | searchAndRescueSystem |
P103542
|
FINISHED |
| Object | COSPAS-SARSAT compatible |
—
|
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: COSPAS-SARSAT compatible | Statement: [INSAT-3DR, searchAndRescueSystem, COSPAS-SARSAT compatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchAndRescueSystem Context triple: [INSAT-3DR, searchAndRescueSystem, COSPAS-SARSAT compatible]
-
A.
searchAndRescueRegion
Indicates that a specified area is designated or used as the operational region for conducting search and rescue activities.
-
B.
typeOfRescue
Indicates the specific method or category of rescue operation performed in a rescue event.
-
C.
SARSystem
chosen
Indicates a system designed to perform search and rescue operations, typically coordinating detection, location, and assistance for persons or objects in distress.
-
D.
rescueCoordinatedBy
Indicates that a rescue operation is organized, directed, or managed by a particular coordinating entity.
-
E.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.