Triple
T12785237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BART Transbay Zone 1 |
E305606
|
entity |
| Predicate | isCoreFor |
P47186
|
FINISHED |
| Object | central San Francisco BART stations |
—
|
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: central San Francisco BART stations | Statement: [BART Transbay Zone 1, isCoreFor, central San Francisco BART stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoreFor Context triple: [BART Transbay Zone 1, isCoreFor, central San Francisco BART stations]
-
A.
isCoreComponentOf
chosen
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
B.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
C.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
-
D.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
E.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5cb3c08190b8e1e22de8b96e17 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.