Triple
T28628576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Wikimedia projects |
E724583
|
entity |
| Predicate | globalCommunity |
P91054
|
FINISHED |
| Object | Wikimedia contributors |
—
|
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: Wikimedia contributors | Statement: [Polish Wikimedia projects, globalCommunity, Wikimedia contributors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalCommunity Context triple: [Polish Wikimedia projects, globalCommunity, Wikimedia contributors]
-
A.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
B.
hasGlobalCommunity
chosen
Indicates that an entity is associated with or participates in a worldwide community or network of people.
-
C.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
D.
originCommunity
Indicates the community, group, or locality from which an entity originally comes or is derived.
-
E.
communalAspect
Indicates that something involves or emphasizes shared participation, ownership, or experience within a group or 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:37 a.m.