Triple
T31676692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Zachary |
E808417
|
entity |
| Predicate | brokeRecordAgainst |
P42667
|
FINISHED |
| Object | Babe Ruth |
—
|
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: Babe Ruth | Statement: [Tom Zachary, brokeRecordAgainst, Babe Ruth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeRecordAgainst Context triple: [Tom Zachary, brokeRecordAgainst, Babe Ruth]
-
A.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
B.
brokeRecord
chosen
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
C.
brokeSoundBarrier
Indicates that an entity achieved a speed exceeding the speed of sound, thereby breaking the sound barrier.
-
D.
wasWorldRecordFor
Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
-
E.
brokeSoundBarrierDate
Indicates the date on which an entity first exceeded the speed of sound.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:03 p.m.