Triple
T35888888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TILO |
E1037727
|
entity |
| Predicate | focusesOnService |
P31
|
FINISHED |
| Object | regional mobility in Ticino |
—
|
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: regional mobility in Ticino | Statement: [TILO, focusesOnService, regional mobility in Ticino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnService Context triple: [TILO, focusesOnService, regional mobility in Ticino]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
branchOfServiceFocus
Indicates that one entity is the primary military or organizational branch of service emphasized, specialized in, or targeted by another entity or activity.
-
C.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
D.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
E.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.