Triple
T36238673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Street Park |
E891446
|
entity |
| Predicate | secondaryModePriority |
P178575
|
FINISHED |
| Object | bicycles |
—
|
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: bicycles | Statement: [Bell Street Park, secondaryModePriority, bicycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryModePriority Context triple: [Bell Street Park, secondaryModePriority, bicycles]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
C.
secondPreferenceWeight
chosen
Indicates the relative importance or influence assigned to an entity when it is considered as a second preference in a choice or ranking.
-
D.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
E.
secondaryOrderingPrinciple
Indicates an additional, subordinate criterion used to order or rank items when a primary ordering principle is already in place.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 4:09 p.m.