Triple
T15951927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV V150 |
E386837
|
entity |
| Predicate | recordSurpassed |
P30975
|
FINISHED |
| Object | world rail speed record set in 1990 |
—
|
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: world rail speed record set in 1990 | Statement: [TGV V150, recordSurpassed, world rail speed record set in 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordSurpassed Context triple: [TGV V150, recordSurpassed, world rail speed record set in 1990]
-
A.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
B.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
C.
recordHeldUntil
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
-
D.
brokeRecordOf
chosen
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
E.
recordStatus
Indicates the current state or condition of a record within a system or process (e.g., active, inactive, pending, or archived).
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.