Triple
T3302255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roald Amundsen |
E69361
|
entity |
| Predicate | searchingFor |
P47887
|
FINISHED |
| Object | missing airship Italia during final flight |
—
|
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: missing airship Italia during final flight | Statement: [Roald Amundsen, searchingFor, missing airship Italia during final flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchingFor Context triple: [Roald Amundsen, searchingFor, missing airship Italia during final flight]
-
A.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
B.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
C.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
D.
typeOfSearch
Indicates the specific kind or category of search operation being performed or requested between entities.
-
E.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a9450481909f0d630e5593085e |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.