Triple
T36337326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremont Fair |
E894821
|
entity |
| Predicate | transportRecommendation |
P28199
|
FINISHED |
| Object | public transit |
—
|
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: public transit | Statement: [Fremont Fair, transportRecommendation, public transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRecommendation Context triple: [Fremont Fair, transportRecommendation, public transit]
-
A.
recommendation
Indicates that one entity suggests, endorses, or advises another entity as suitable or beneficial for a particular purpose or context.
-
B.
transportAdvisory
chosen
Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
-
C.
transportFocus
Indicates that an entity is the primary object or subject of a transportation action or movement event.
-
D.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
E.
commendationType
Indicates the specific category or kind of commendation associated with an action or relationship.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:09 p.m.