Triple
T18367283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Kaguya |
E440079
|
entity |
| Predicate | setsTaskFor |
P115201
|
FINISHED |
| Object | her suitors |
—
|
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 suitors | Statement: [Princess Kaguya, setsTaskFor, her suitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsTaskFor Context triple: [Princess Kaguya, setsTaskFor, her suitors]
-
A.
setTaskFor
Indicates assigning or configuring a specific task to be carried out for a particular entity or context.
-
B.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
C.
targetTask
Indicates that one entity is the specific task or objective that another entity is aiming to perform, achieve, or operate on.
-
D.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
-
E.
assignedToWorkBy
chosen
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
- 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.