Triple
T18367287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Kaguya |
E440079
|
entity |
| Predicate | leavesBehind |
P56600
|
FINISHED |
| Object | her adoptive parents |
—
|
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: her adoptive parents | Statement: [Princess Kaguya, leavesBehind, her adoptive parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leavesBehind Context triple: [Princess Kaguya, leavesBehind, her adoptive parents]
-
A.
leavesIn
Indicates that one entity departs from or exits another entity, such as a place, group, or state, at a particular time or under certain conditions.
-
B.
leaves
chosen
Indicates that an entity departs from or goes away from another entity, location, or situation.
-
C.
leavesCluesFor
Indicates that one entity intentionally or unintentionally provides hints, traces, or evidence that can be used by another entity to discover, understand, or infer something.
-
D.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
E.
leavesEarthWith
Indicates that one entity departs from Earth together with another entity, accompanying them in leaving the planet.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174f5f448190a1fc67d3039aadd9 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.