Triple
T30705004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keynote Records |
E781726
|
entity |
| Predicate | hasReissueOn |
P202654
|
FINISHED |
| Object | CD |
—
|
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: CD | Statement: [Keynote Records, hasReissueOn, CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissueOn Context triple: [Keynote Records, hasReissueOn, CD]
-
A.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
B.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
-
C.
hasReissuePeriod
Indicates the time span during which something (such as a document, license, or product) may be reissued or renewed.
-
D.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
E.
canBeReissued
Indicates that something is eligible to be issued again, such as a document, license, or item that can be re-granted or re-produced after its initial issuance.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_6a00a74afb3c8190a274bf6681950aa3 |
completed | May 10, 2026, 3:42 p.m. |
Created at: April 29, 2026, 8:35 p.m.