Triple
T31105189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naib of Sietch Tabr |
E792773
|
entity |
| Predicate | governsResources |
P760
|
FINISHED |
| Object | water of Sietch Tabr |
—
|
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: water of Sietch Tabr | Statement: [Naib of Sietch Tabr, governsResources, water of Sietch Tabr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsResources Context triple: [Naib of Sietch Tabr, governsResources, water of Sietch Tabr]
-
A.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
-
B.
governsRightsOf
Indicates that one entity has legal or authoritative control over determining, defining, or regulating the rights of another entity.
-
C.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governingSee
Indicates that a governing authority observes, oversees, or monitors another entity or situation.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 29, 2026, 9:03 p.m.