Triple
T6800210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金本知憲 |
E156163
|
entity |
| Predicate | 連続試合出場記録 |
P14549
|
FINISHED |
| Object | 1766試合 |
—
|
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: 1766試合 | Statement: [金本知憲, 連続試合出場記録, 1766試合]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 連続試合出場記録 Context triple: [金本知憲, 連続試合出場記録, 1766試合]
-
A.
consecutiveGamesRecordHeldFrom
Indicates that one entity held the record for most consecutive games played starting from a specified point in time.
-
B.
consecutiveGamesRecordHeldUntil
Indicates that an entity held the record for most consecutive games until a specified later point in time or event.
-
C.
consecutiveGamesPlayed
chosen
Indicates that an entity has participated in a series of games without interruption, one immediately following another.
-
D.
consecutiveGamesStarted
Indicates that one entity has started in a series of games without interruption, directly following each previous game in sequence.
-
E.
longestUnbeatenStreak
Indicates the relationship where an entity holds the greatest continuous sequence of events (such as games or matches) without a loss compared to others.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e457408190a0ad9b0c48d8147c |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.