Triple
T36079470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astor region |
E1043599
|
entity |
| Predicate | hasDomainOf |
P68688
|
FINISHED |
| Object | Astori Shina |
—
|
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: Astori Shina | Statement: [Astor region, hasDomainOf, Astori Shina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainOf Context triple: [Astor region, hasDomainOf, Astori Shina]
-
A.
containsDomain
chosen
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
B.
hasPossibleDomain
Indicates that a property or relation may apply to, or be defined over, a particular class or type of entities, without asserting that this is its only or actual domain.
-
C.
indicatesDomain
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
D.
hasDomainAbove
Indicates that one entity’s domain or scope is positioned higher or supersedes another entity’s domain in a hierarchical or layered structure.
-
E.
hasLegalDomain
Indicates that a legal rule, right, obligation, or concept applies within a specific jurisdiction, legal system, or domain of law.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.