Triple
T30083708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee concert for Sir Henry J. Wood |
E764541
|
entity |
| Predicate | hasMainHonouree |
P3737
|
FINISHED |
| Object | Sir Henry J. Wood |
—
|
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: Sir Henry J. Wood | Statement: [Jubilee concert for Sir Henry J. Wood, hasMainHonouree, Sir Henry J. Wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainHonouree Context triple: [Jubilee concert for Sir Henry J. Wood, hasMainHonouree, Sir Henry J. Wood]
-
A.
hasNotableHonoree
chosen
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
B.
honoureeNationality
Indicates that the honoured person has the specified nationality.
-
C.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
D.
honoureeParticipatedIn
Indicates that the honouree took part in, or was involved in, a specific event, activity, or occasion.
-
E.
hasNotableHonor
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: April 29, 2026, 7:03 p.m.