Triple
T34664870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Docker River |
E890223
|
entity |
| Predicate | hasRemoteCommunityStatus |
P55240
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Docker River, hasRemoteCommunityStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemoteCommunityStatus Context triple: [Docker River, hasRemoteCommunityStatus, true]
-
A.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
-
B.
hasRemoteCommunities
chosen
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
statusOfCommunity
Indicates the current condition, state, or standing of a community at a given point in time.
-
E.
statusInCommunity
Indicates the social standing, role, or level of acceptance an entity holds within a particular community.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
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:04 a.m.