Triple
T29266146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-net tram services |
E741980
|
entity |
| Predicate | serviceStandard |
P67069
|
FINISHED |
| Object | minimum frequency targets |
—
|
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: minimum frequency targets | Statement: [R-net tram services, serviceStandard, minimum frequency targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStandard Context triple: [R-net tram services, serviceStandard, minimum frequency targets]
-
A.
hasServiceStandard
chosen
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
-
B.
serviceUniform
Indicates that one entity is wearing or associated with a standardized uniform used for official or professional service.
-
C.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
D.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
E.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 12:45 p.m.