Triple
T15065484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Metro (defunct) |
E379743
|
entity |
| Predicate | servedUsers |
P14200
|
FINISHED |
| Object | office commuters in Cyber City |
—
|
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: office commuters in Cyber City | Statement: [Rapid Metro (defunct), servedUsers, office commuters in Cyber City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedUsers Context triple: [Rapid Metro (defunct), servedUsers, office commuters in Cyber City]
-
A.
servesUsers
chosen
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
B.
servesUsersFrom
Indicates that an entity provides services or resources to users originating from or associated with a specified source or location.
-
C.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
D.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another entity.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeea750c819082d8823c9ab6c5a2 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.