Triple
T35651307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Metro |
E1030158
|
entity |
| Predicate | targetRiderGroup |
P10541
|
FINISHED |
| Object | 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: commuters | Statement: [Sun Metro, targetRiderGroup, commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRiderGroup Context triple: [Sun Metro, targetRiderGroup, commuters]
-
A.
targetsGroup
chosen
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
B.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
C.
targetTouristGroup
Indicates that an entity is the intended or actual focus of actions, services, or attention directed toward a specific group of tourists.
-
D.
targetStudentGroup
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
E.
targetRole
Indicates the specific role or function that an entity is intended or designated to fulfill in a given context.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:05 p.m.