Triple
T19071270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diwan Abatur |
E466795
|
entity |
| Predicate | ontologicalCategoryDescribed |
P129410
|
FINISHED |
| Object | uthras |
—
|
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: uthras | Statement: [Diwan Abatur, ontologicalCategoryDescribed, uthras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ontologicalCategoryDescribed Context triple: [Diwan Abatur, ontologicalCategoryDescribed, uthras]
-
A.
hasOntologicalCategory
chosen
Indicates that an entity belongs to, or is classified under, a specific ontological category or type within a conceptual framework.
-
B.
ontologicalAspect
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
C.
ontologicalClaimAbout
Indicates that one entity makes a statement or assertion about the fundamental nature, existence, or categorization of another entity.
-
D.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
E.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19fa6948190bdf8e8ec022e12f2 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.