Triple
T32604633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britain (legendary) |
E833472
|
entity |
| Predicate | hasAssociatedHero |
P63978
|
FINISHED |
| Object | King Arthur |
—
|
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: King Arthur | Statement: [Britain (legendary), hasAssociatedHero, King Arthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedHero Context triple: [Britain (legendary), hasAssociatedHero, King Arthur]
-
A.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
B.
hasNotableHero
chosen
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
C.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
D.
hasEponymousHero
Indicates that a work or narrative features a hero whose name is the same as, or gives its name to, the work itself.
-
E.
associatedWithSuperhero
Indicates that one entity has a notable connection, link, or involvement with a superhero 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:05 a.m.