Triple
T30346665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyubey |
E771884
|
entity |
| Predicate | extracts |
P10922
|
FINISHED |
| Object | soul |
—
|
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: soul | Statement: [Kyubey, extracts, soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extracts Context triple: [Kyubey, extracts, soul]
-
A.
extractedIn
Indicates that one entity is obtained, derived, or separated from another entity through an extraction process.
-
B.
resourceExtracted
chosen
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
popularExcerpt
Indicates that a given excerpt is widely liked, frequently referenced, or otherwise considered popular among users or audiences.
-
E.
extractedBy
Indicates that one entity is obtained, derived, or separated from another entity through some extraction process or method.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682084db081909e261c5bbae024e3 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.