Triple
T24001390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Diridon |
E594256
|
entity |
| Predicate | futureServedBy |
P90369
|
FINISHED |
| Object | California High-Speed Rail |
—
|
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: California High-Speed Rail | Statement: [San Jose Diridon, futureServedBy, California High-Speed Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureServedBy Context triple: [San Jose Diridon, futureServedBy, California High-Speed Rail]
-
A.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
B.
laterServedBy
chosen
Indicates that one entity is subsequently served or provided service by another entity at a later time.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
-
E.
presentlyServedBy
Indicates that an entity is currently being provided with service or attended to by 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d464f1988190a0a9352c1ec214eb |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:39 p.m.