Triple
T13444730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT-5 |
E320449
|
entity |
| Predicate | achievedRecordOn |
P83896
|
FINISHED |
| Object | 1965-08-21 |
—
|
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: 1965-08-21 | Statement: [GT-5, achievedRecordOn, 1965-08-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedRecordOn Context triple: [GT-5, achievedRecordOn, 1965-08-21]
-
A.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
B.
achievedOn
chosen
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
C.
brokeRecord
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
D.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
E.
previousRecordHolder
Indicates that one entity was the former holder of a particular record before another entity surpassed or replaced it.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef5f610819092cad33ef72075ff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.