Triple
T30482183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koimonogatari |
E775614
|
entity |
| Predicate | hasArcName |
P115897
|
FINISHED |
| Object | Koimonogatari: Hitagi End |
—
|
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: Koimonogatari: Hitagi End | Statement: [Koimonogatari, hasArcName, Koimonogatari: Hitagi End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArcName Context triple: [Koimonogatari, hasArcName, Koimonogatari: Hitagi End]
-
A.
hasArc
Indicates that there is a directed connection or edge from one entity to another, often representing a link in a graph or network.
-
B.
hasArcElement
Indicates that one entity includes or is associated with an arc-shaped component or element.
-
C.
hasArcType
Indicates that one entity is associated with, or characterized by, a specific type or category of arc.
-
D.
nombreArcs
Indicates the number of arcs (directed edges or connections) associated with a given element or structure.
-
E.
arcName
chosen
Indicates that a named label or identifier is assigned to a specific arc (directed connection) in a structure such as a graph or network.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 8:12 p.m.