Triple
T34543462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StreetComplete |
E886862
|
entity |
| Predicate | supportsOfflineUse |
P104010
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [StreetComplete, supportsOfflineUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOfflineUse Context triple: [StreetComplete, supportsOfflineUse, yes]
-
A.
isDesignedForOfflineUse
Indicates that something is intended or optimized to function without requiring an active network or internet connection.
-
B.
supportsOnlineContent
Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
offlineCapability
chosen
Indicates that an entity can function or provide its intended service without requiring a continuous network or internet connection.
-
E.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.