Triple
T36420465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | recipientFullName |
P31292
|
FINISHED |
| Object | Guy Penrose Gibson |
—
|
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: Guy Penrose Gibson | Statement: [Victoria Cross to Guy Gibson, recipientFullName, Guy Penrose Gibson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recipientFullName Context triple: [Victoria Cross to Guy Gibson, recipientFullName, Guy Penrose Gibson]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
bearerPersonalName
Indicates that a personal name is borne or held by a particular entity (the bearer).
-
C.
senderName
Indicates the name or identifier of the entity that sends or originates a message, item, or communication in the relationship.
-
D.
granteeFullName
chosen
Indicates the complete personal name of the entity that receives a grant or is designated as the grantee.
-
E.
creatorFullName
Indicates the full personal name of the entity that created or authored 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.