Triple
T30520466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gram |
E776679
|
entity |
| Predicate | notableOwnerRole |
P207282
|
FINISHED |
| Object | Sigurd as dragon slayer |
E435371
|
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: Sigurd as dragon slayer | Statement: [Gram, notableOwnerRole, Sigurd as dragon slayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOwnerRole Context triple: [Gram, notableOwnerRole, Sigurd as dragon slayer]
-
A.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
B.
notableRecipientRole
Indicates that an entity has received a notable award, honor, or recognition specifically in the capacity of a particular role or position.
-
C.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
-
D.
notableOfficerRole
Indicates that an entity holds or has held a particularly significant or distinguished officer position within an organization or institution.
-
E.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
- F. None of above. chosen
Provenance (5 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27be71f2cc8190a6e684d7a95fdbd5 |
completed | June 9, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:17 p.m.