Triple
T31917888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinobu Oshino |
E814884
|
entity |
| Predicate | sharesLifeLinkWith |
P199316
|
FINISHED |
| Object | Koyomi Araragi |
—
|
NE NERFINISHED |
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: Koyomi Araragi | Statement: [Shinobu Oshino, sharesLifeLinkWith, Koyomi Araragi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLifeLinkWith Context triple: [Shinobu Oshino, sharesLifeLinkWith, Koyomi Araragi]
-
A.
sharesLifeboatWith
Indicates that two or more entities are occupying or using the same lifeboat together.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesLifewaysAmong
Indicates that multiple entities participate in and transmit common cultural practices, values, or ways of living among one another.
-
D.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
E.
sharesNetwork
Indicates that two or more entities are connected to and operate within the same network.
- F. None of above. chosen
Provenance (4 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: May 1, 2026, 12:02 a.m.