Triple
T25745887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexus F |
E648342
|
entity |
| Predicate | usesTestTrack |
P159217
|
FINISHED |
| Object | Fuji Speedway |
—
|
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: Fuji Speedway | Statement: [Lexus F, usesTestTrack, Fuji Speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTestTrack Context triple: [Lexus F, usesTestTrack, Fuji Speedway]
-
A.
openedAsTestTrack
Indicates that something was initially opened or put into operation specifically as a test track rather than as a full, regular facility.
-
B.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
-
C.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
D.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
E.
titleTrackUsedAs
Indicates that a work serves as the title track for another work, such as an album, film, or series.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1e9dd081908c70074c8aa49e51 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 3:51 a.m.