Triple
T32683805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E6 series Shinkansen |
E835661
|
entity |
| Predicate | couplesWith |
P3984
|
FINISHED |
| Object | E5 series Shinkansen |
—
|
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: E5 series Shinkansen | Statement: [E6 series Shinkansen, couplesWith, E5 series Shinkansen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couplesWith Context triple: [E6 series Shinkansen, couplesWith, E5 series Shinkansen]
-
A.
couplesTo
chosen
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
-
B.
couplesQuarks
Indicates an interaction or relationship in which quarks are linked or coupled to each other or to another entity through a fundamental force or mechanism.
-
C.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
D.
spouseInDuo
Indicates that two individuals are spouses who perform or appear together as a duo.
-
E.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7ea33c48190a88f71db09d595e4 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.