Triple
T70784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco cable car system |
E1416
|
entity |
| Predicate | secondaryUse |
P2114
|
FINISHED |
| Object | local transportation |
—
|
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: local transportation | Statement: [San Francisco cable car system, secondaryUse, local transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryUse Context triple: [San Francisco cable car system, secondaryUse, local transportation]
-
A.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eaa0df88190add55579b2b9fd02 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.