Triple
T34166388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Coast Guard Station Sandy Hook |
E876423
|
entity |
| Predicate | performsOperationType |
P24
|
FINISHED |
| Object | search and rescue |
—
|
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: search and rescue | Statement: [U.S. Coast Guard Station Sandy Hook, performsOperationType, search and rescue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsOperationType Context triple: [U.S. Coast Guard Station Sandy Hook, performsOperationType, search and rescue]
-
A.
performsOperation
chosen
Indicates that one entity carries out or executes a specific operation on or for another entity.
-
B.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
C.
typeOfOperation
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
D.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
E.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:54 a.m.