Triple
T27890415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninth Street Genji |
E705337
|
entity |
| Predicate | hasPrimaryResidenceType |
P542
|
FINISHED |
| Object | kyūte (aristocratic residence) |
—
|
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: kyūte (aristocratic residence) | Statement: [Ninth Street Genji, hasPrimaryResidenceType, kyūte (aristocratic residence)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryResidenceType Context triple: [Ninth Street Genji, hasPrimaryResidenceType, kyūte (aristocratic residence)]
-
A.
hasTraditionalResidenceType
Indicates that an entity is associated with a particular customary or historically established type of residence.
-
B.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
hasCanonicalResidence
Indicates that an entity has an officially recognized primary place of residence or domicile.
-
D.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
E.
residenceStatus
Indicates the type or condition of an entity’s living arrangement or place of residence in relation to a specified location.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 27, 2026, 6:35 p.m.