Triple
T37974342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding Everett Ruess |
E947379
|
entity |
| Predicate | investigatesEvent |
P16515
|
FINISHED |
| Object | 1934 disappearance of Everett Ruess |
—
|
NE NERFINISHED |
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: 1934 disappearance of Everett Ruess | Statement: [Finding Everett Ruess, investigatesEvent, 1934 disappearance of Everett Ruess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigatesEvent Context triple: [Finding Everett Ruess, investigatesEvent, 1934 disappearance of Everett Ruess]
-
A.
investigatedEvent
chosen
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
B.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
investigatesIn
Indicates that an entity conducts an investigation or inquiry within, or focused on, a particular context, location, or domain.
-
D.
investigatesAt
Indicates that an entity conducts an investigation or research activity at a specific location or institution.
-
E.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.