Triple
T615514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC-295 Kingfisher |
E12194
|
entity |
| Predicate | serviceDomain |
P5621
|
FINISHED |
| Object | aerial 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: aerial search and rescue | Statement: [CC-295 Kingfisher, serviceDomain, aerial search and rescue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceDomain Context triple: [CC-295 Kingfisher, serviceDomain, aerial search and rescue]
-
A.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
B.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
C.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
D.
serviceClass
chosen
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.