Triple
T25009924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TWB |
E625952
|
entity |
| Predicate | usedByInformationSystems |
P8459
|
FINISHED |
| Object | online journey planners |
—
|
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: online journey planners | Statement: [TWB, usedByInformationSystems, online journey planners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByInformationSystems Context triple: [TWB, usedByInformationSystems, online journey planners]
-
A.
usedBySystem
chosen
Indicates that something is utilized or operated by a particular system.
-
B.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
C.
usedInComputingSystems
Indicates that something is employed or applied within computing systems, such as hardware, software, or digital infrastructures, to perform functions or operations.
-
D.
usesDataSystem
Indicates that one entity employs, accesses, or relies on a particular data system to perform its functions or operations.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:05 a.m.