Triple
T2396216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelia Earhart |
E47656
|
entity |
| Predicate | declaredDead |
P9134
|
FINISHED |
| Object | 1939-01-05 |
—
|
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: 1939-01-05 | Statement: [Amelia Earhart, declaredDead, 1939-01-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredDead Context triple: [Amelia Earhart, declaredDead, 1939-01-05]
-
A.
declaredDeadAt
chosen
Indicates that an authority or official source has formally pronounced an entity as dead at a specific time or place.
-
B.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
-
C.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
D.
diedWhile
Indicates that one entity ceased to live during the occurrence or performance of another specified event or activity.
-
E.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c4a8bc819086892a75caac0207 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.