Triple
T29761354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy (lunar crater) |
E753778
|
entity |
| Predicate | honoursPerson |
P75580
|
FINISHED |
| Object | George Biddell Airy |
—
|
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: George Biddell Airy | Statement: [Airy (lunar crater), honoursPerson, George Biddell Airy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursPerson Context triple: [Airy (lunar crater), honoursPerson, George Biddell Airy]
-
A.
honorsPerson
chosen
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
B.
honoursHolder
Indicates that one entity is the designated recipient or bearer of a particular honour, award, or distinction conferred by another entity.
-
C.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
D.
honouredPersonOccupation
Indicates that the honored person is or was associated with a particular occupation or professional role.
-
E.
honoursPersonBirthName
Indicates that an entity formally recognizes or commemorates a person using the name they were given at birth.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f673d041448190a414a19cf28b09d2 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 8:33 p.m.