Triple
T28924939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood and Thunder |
E733614
|
entity |
| Predicate | notableGroupDepicted |
P35849
|
FINISHED |
| Object | Navajo people |
E46796
|
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: Navajo people | Statement: [Blood and Thunder, notableGroupDepicted, Navajo people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGroupDepicted Context triple: [Blood and Thunder, notableGroupDepicted, Navajo people]
-
A.
notableCharacterGroup
chosen
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
-
B.
notableDepictionBy
Indicates that an entity is significantly portrayed or represented by a particular creator, work, or medium.
-
C.
notablePortraitSubject
Indicates that the subject is a person who is prominently or famously depicted in a portrait created by the other entity.
-
D.
notableForDepicting
Indicates that something is recognized or distinguished specifically for portraying or representing a particular subject, theme, or scene.
-
E.
notableOrganizationDepicted
Indicates that a notable organization is visually represented or portrayed in the subject (such as an image, work, or media item).
- F. None of above.
Provenance (4 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d420d1e08190a54e2a092510c93c |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
Created at: April 28, 2026, 8:22 a.m.