Triple
T29516497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Wikipedia |
E748810
|
entity |
| Predicate | hasCommunityProcess |
P202322
|
FINISHED |
| Object | Articles for deletion |
—
|
NE NERFINISHED |
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: Articles for deletion | Statement: [English Wikipedia, hasCommunityProcess, Articles for deletion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityProcess Context triple: [English Wikipedia, hasCommunityProcess, Articles for deletion]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunitySupport
Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
-
C.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
D.
hasComponentCommunity
Indicates that an entity includes or is composed of a specific community as one of its constituent parts.
-
E.
hasCommunityFunction
Indicates that an entity serves or provides a function, role, or service that benefits or supports a community.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
| PDg | Predicate description generation | batch_6a007240adac819087ab65e9733c384f |
completed | May 10, 2026, 11:55 a.m. |
Created at: April 28, 2026, 4:37 p.m.