Triple
T31638900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trolleybus Line 1 |
E807389
|
entity |
| Predicate | hasPriorityUsers |
P158607
|
FINISHED |
| Object | daily commuters |
—
|
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: daily commuters | Statement: [Trolleybus Line 1, hasPriorityUsers, daily commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriorityUsers Context triple: [Trolleybus Line 1, hasPriorityUsers, daily commuters]
-
A.
hasPriorityIssue
Indicates that an entity is associated with an issue that is marked as high or urgent priority.
-
B.
hasCommunityPriority
Indicates that something is given precedence or special importance based on community needs, values, or preferences.
-
C.
hasUsers
chosen
Indicates that an entity is associated with one or more users who use, own, or are linked to it.
-
D.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
E.
supportsPriority
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:48 p.m.