Triple
T28644082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Wikiversity |
E725005
|
entity |
| Predicate | supportsLearningCommunities |
P203634
|
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: [Tamil Wikiversity, supportsLearningCommunities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLearningCommunities Context triple: [Tamil Wikiversity, supportsLearningCommunities, true]
-
A.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
B.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
C.
supportsCommunityGuidelines
Indicates that an entity upholds, complies with, or actively promotes the established community guidelines.
-
D.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
E.
formedCommunityWith
Indicates that two or more entities came together to establish or join the same community or collective group.
- F. None of above. chosen
Provenance (4 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
| PDg | Predicate description generation | batch_6a01bb0584608190a27ad07f095ea7fd |
completed | May 11, 2026, 11:18 a.m. |
Created at: April 28, 2026, 4:47 a.m.