Triple
T24218330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strætó |
E601367
|
entity |
| Predicate | mobileAppFunction |
P84759
|
FINISHED |
| Object | journey planning |
—
|
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: journey planning | Statement: [Strætó, mobileAppFunction, journey planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileAppFunction Context triple: [Strætó, mobileAppFunction, journey planning]
-
A.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
B.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
C.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
D.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
E.
featuresAbility
chosen
Indicates that one entity possesses, includes, or provides a particular ability or capability associated with 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820a80ec8190bd11f08f7733843d |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.