Triple
T29670556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man'yōshū poets |
E750656
|
entity |
| Predicate | socialRange |
P108117
|
FINISHED |
| Object | emperors |
—
|
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: emperors | Statement: [Man'yōshū poets, socialRange, emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRange Context triple: [Man'yōshū poets, socialRange, emperors]
-
A.
socialCircle
Indicates that one entity belongs to, or is part of, the group of people with whom another entity regularly interacts socially.
-
B.
socialRelations
chosen
Indicates a relationship in which entities are connected through social ties, interactions, or roles within a social context.
-
C.
socialComposition
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
D.
engagementRange
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
E.
relationshipScope
Indicates the contextual boundaries or extent within which a particular relationship between entities is defined or considered valid.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 7:04 p.m.