Triple
T36880833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelia Earhart Airport |
E911472
|
entity |
| Predicate | hasCommemorationSubject |
P63144
|
FINISHED |
| Object | Amelia Earhart |
E47656
|
NE 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: Amelia Earhart | Statement: [Amelia Earhart Airport, hasCommemorationSubject, Amelia Earhart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorationSubject Context triple: [Amelia Earhart Airport, hasCommemorationSubject, Amelia Earhart]
-
A.
isCommemorationSubject
chosen
Indicates that an entity serves as the focus or object of a commemorative act, event, or artifact.
-
B.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
C.
hasCommemorativeObject
Indicates that one entity possesses or is associated with an object specifically intended to commemorate or honor a person, event, or occasion.
-
D.
hasCommemorationName
Indicates that an entity has a specific name used to commemorate or honor a person, event, or concept.
-
E.
hasTypeOfPersonCommemorated
Indicates that something is associated with or dedicated to a person of a specified type or role being commemorated.
- F. None of above.
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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40822d619c81909183423c5d27036f |
completed | June 28, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.