Triple
T8538981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MuniMobile app |
E202147
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | Muni |
E6878
|
NE 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: Muni | Statement: [MuniMobile app, brand, Muni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muni Context triple: [MuniMobile app, brand, Muni]
-
A.
Muni
Muni is an honorific title traditionally used in Indian culture to denote a sage, seer, or revered spiritual teacher.
-
B.
Muni
chosen
Muni is San Francisco’s primary public transit agency, operating buses, light rail, historic streetcars, and the city’s iconic cable cars.
-
C.
Metros
Metros is the nickname historically used for the MetroStars, the former Major League Soccer team now known as the New York Red Bulls.
-
D.
Muni Passport
Muni Passport is a time-based transit pass that provides unlimited rides on San Francisco’s Muni system, including historic streetcars and cable cars, for a set number of days.
-
E.
Metropolitano
Metropolitano is a former operator of the San Martín Line, a railway service in Argentina.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a7441c8190980c3516073422fe |
completed | March 31, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d953fd0819094958d2b5a5a8e13 |
completed | April 2, 2026, 1:22 p.m. |
Created at: March 30, 2026, 6:18 p.m.