Triple
T8301807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikinews |
E194364
|
entity |
| Predicate | hasDiscussionSpace |
P31864
|
FINISHED |
| Object | community portal |
—
|
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: community portal | Statement: [Ukrainian Wikinews, hasDiscussionSpace, community portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscussionSpace Context triple: [Ukrainian Wikinews, hasDiscussionSpace, community portal]
-
A.
hasDiscussionSystem
Indicates that an entity is equipped with or supports a system for facilitating discussions or conversations.
-
B.
hasDiscussionPages
chosen
Indicates that an entity is associated with one or more pages where discussions or conversations about it take place.
-
C.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
D.
containsDiscussionOf
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
E.
hasAdditionalForum
Indicates that an entity is associated with one or more supplementary or secondary discussion forums beyond its primary forum.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e891030819097f4a26992a8b469 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.