Triple
T33382386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umonhonti |
E854817
|
entity |
| Predicate | traditionallyGuardedBy |
P79175
|
FINISHED |
| Object | Omaha religious leaders |
—
|
LITERAL 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: Omaha religious leaders | Statement: [Umonhonti, traditionallyGuardedBy, Omaha religious leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyGuardedBy Context triple: [Umonhonti, traditionallyGuardedBy, Omaha religious leaders]
-
A.
historicallyGuardedBy
chosen
Indicates that an entity was protected or defended by another entity during a past historical period.
-
B.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
C.
typicalGuard
Indicates that an entity commonly or characteristically serves in a guarding or protective role relative to another entity or context.
-
D.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
E.
isTraditionallyOccupiedBy
Indicates that a place, territory, or role has historically and customarily been inhabited or held by a particular group or type of 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:35 a.m.