Triple
T22267679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly Grand Descent |
E550391
|
entity |
| Predicate | marksOriginOf |
P137413
|
FINISHED |
| Object | Japanese imperial line |
—
|
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: Japanese imperial line | Statement: [Heavenly Grand Descent, marksOriginOf, Japanese imperial line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksOriginOf Context triple: [Heavenly Grand Descent, marksOriginOf, Japanese imperial line]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
marksLocationOf
Indicates that one entity serves as a marker, sign, or indicator specifying the location of another entity.
-
C.
maskOrigin
Indicates that one entity serves as the original source or basis from which another entity’s mask or masking representation is derived.
-
D.
depictsOriginOf
Indicates that one entity visually represents or illustrates the source, beginning, or point of origin of another entity.
-
E.
describesOriginOf
chosen
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bd0ea88190b3574883b695d56c |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:39 p.m.