Triple
T27286860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Turpin |
E688499
|
entity |
| Predicate | recordSummary |
P31882
|
FINISHED |
| Object | held world middleweight title briefly in 1951 |
—
|
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: held world middleweight title briefly in 1951 | Statement: [Randy Turpin, recordSummary, held world middleweight title briefly in 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordSummary Context triple: [Randy Turpin, recordSummary, held world middleweight title briefly in 1951]
-
A.
recordDetail
Indicates that one entity stores or documents specific information or attributes about another entity.
-
B.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
-
C.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
D.
recordStatus
Indicates the current state or condition of a record within a system or process (e.g., active, inactive, pending, or archived).
-
E.
summarizes
chosen
Indicates that one entity provides a concise representation or overview of the main points or content of another entity.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 11:12 a.m.