Triple
T25689221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashihara-no-Nakatsukuni |
E644152
|
entity |
| Predicate | hasDomainAbove |
P159795
|
FINISHED |
| Object | Takamagahara |
—
|
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: Takamagahara | Statement: [Ashihara-no-Nakatsukuni, hasDomainAbove, Takamagahara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainAbove Context triple: [Ashihara-no-Nakatsukuni, hasDomainAbove, Takamagahara]
-
A.
containsDomain
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.
isElevatedAbove
Indicates that one entity is positioned at a higher vertical level or altitude than another entity.
-
D.
hasDomainFeature
Indicates that something possesses or is characterized by a specific feature or attribute within a particular domain or context.
-
E.
hasDominated
Indicates that one entity has exercised overwhelming control, superiority, or influence over another, often in a sustained or decisive manner.
- F. None of above. chosen
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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbbfd64481908dd4252869bd5ca2 |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 8:14 p.m.